Re: Problem with umount

[Daniel Harvey <daniel@xxxxxxxxxxxxxxx>]

Hi Jari,

Thanks for your response.

Re: EXT3. Yes. I set this filesystem up "years" ago. I originally
created an ext3, then modified to remove the journal based upon your
advice on this mailing list - I just did not rename the ".fs.ext3" file.
Note that mount shows ext2.

Re: mount/umount. Your explanation makes sense, however, "it used to
work!". Let me explain:

     1. I mount the loop filesystem using your option 3 below. 
     2. Gnome desktop (nautilus) displays the mount on the desktop and
        within nautilus itself in graphical form.
     3. To unmount the loop device, I right click on the icon and select
        "Unmount Volume".
     4. This "used to work" up until about a month ago. When I do this
        now, the operation fails with the message: "Unable to unmount
        the selected volume." with the details

    "umount: /dev/loop4 not mounted"
    "Error: umount failed"

I am trying to establish whether something in mount/umount or in Gnome
nautilus has changed... any thoughts?

BTW, I've reported this elsewhere at https://launchpad.net/bugs/84201

Cheers,
Daniel.
-- 
Daniel Harvey <daniel@xxxxxxxxxxxxxxx>

On Sat, 2007-03-17 at 20:53 +0200, Jari Ruusu wrote:
> 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"
> 



-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/