Messages in this thread | | | Date | Sun, 30 Jul 2000 21:11:29 +0200 | From | Walter Hofmann <> | Subject | Re: crypto loop bug |
| |
On Sun, 30 Jul 2000, Ragnar Hojland Espinosa wrote:
> Actually the bug is the opposite :) ...
I don't think so.
> > frodo:/home/wh # /usr/local/bin/losetup -e serpent /dev/loop0 /usr/local/loop/wh > > Password : correct password > > frodo:/home/wh # /sbin/e2fsck /dev/loop0 > > e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09 > > Group descriptors look bad... trying backup blocks... > > /sbin/e2fsck: Bad magic number in super-block while trying to open /dev/loop0 > > frodo:/home/wh # mount /dev/loop0 /mnt > > frodo:/home/wh # umount /mnt > > frodo:/home/wh # /sbin/e2fsck /dev/loop0 > > e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09 > > /dev/loop0: clean, 4650/81920 files, 66139/163840 blocks > > Since you have already set up the loop device with the right password, the > first fsck shouldn't fail.
I previously set it up with the wrong password (you didn't quote these commands). Then I deleted it. But after setting it up with the right password the old data is still there (or so it seems).
> And since umount doesn't automagically losetup > -d /dev/loop0, it should not invalidate it's settings (password in this > case)
It seems that it is the mount command that invalidates the old pages as mount works correctly and I can access the filesystem after mounting (without errors), although fsck failed.
Walter
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |