Daniel Harvey wrote:
> My fstab mount line represents the following:
>
> /media/usbdisk/.fs.ext3 --> /dev/loop4 --> /media/usbdisk/fs ext2
> file containing EXT3 filesystem --> loop device --> mounted EXT3
> filesystem
That is journaling file system on file backed loop.
loop-AES README section 2.2.
> The problem is that in the past, "umount /dev/loop4" worked, but NOT any
> more.
There are three ways to mount loop devices:
1) Do loop setup/teardown manually:
losetup -e AES128 -K foo.gpg /dev/loop4 /dev/hda999
mount -t ext3 /dev/loop4 /mnt
umount /mnt (or umount /dev/loop4 )
losetup -d /dev/loop4
2) Let mount/umount do loop setup/teardown for you:
mount -t ext3 /dev/hda999 /mnt -o loop=/dev/loop4,encryption=AES128,gpgkey=foo.gpg
umount /mnt (or umount /dev/hda999 )
3) The fstab way, mount/umount do loop setup/teardown for you:
/etc/fstab line:
/dev/hda999 /mnt ext3 defaults,noauto,loop=/dev/loop4,encryption=AES128,gpgkey=foo.gpg,user=daniel 0 0
mount /mnt
umount /mnt (or umount /dev/hda999 )
> However mount shows:
>
> /media/usbdisk/.fs.ext3 on /media/usbdisk/fs type ext2
> (rw,nosuid,nodev,loop=/dev/loop4,user=daniel)
Looks like you used method (1) earlier and are now using method (3). umount
needs mountpoint directory or backing device that was used at mount time. If
you didn't mount /dev/loop4 device directly, then you should not expect
"umount /dev/loop4" to work either.
Try "umount /media/usbdisk/fs" or "umount /media/usbdisk/.fs.ext3"
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
