Yes, /media/usbdisk is a mounted USB device, and the mount point is a directory 'fs' within this.
I've done some more checking and I don't believe this is related to the problem. The problem appears to be related to mount/umount and the use of loop devices.
The problem is that in the past, "umount /dev/loop4" worked, and this is the command that the Gnome interface is executing.
My setup is as follows:
daniel@elvandar:~$ dpkg -S /bin/umount
diversion by loop-aes-utils from: /bin/umount
diversion by loop-aes-utils to: /bin/umount.orig
mount, loop-aes-utils: /bin/umount
daniel@elvandar:~$ dpkg -l mount loop-aes-utils
||/ Name Version Description
+++-==============-==============-============================================
ii loop-aes-utils 2.12r-11 Tools for mounting and manipulating filesyst
ii mount 2.12r-11ubuntu Tools for mounting and manipulating filesyst
Yes, /media/usbdisk is a mounted USB device, and the mount point is a directory 'fs' within this.
I've done some more checking and I don't believe this is related to the problem. The problem appears to be related to mount/umount and the use of loop devices.
My mount line represents the following:
/media/ usbdisk/ .fs.ext3 --> /dev/loop4 --> /media/usbdisk/fs ext2
file containing EXT3 filesystem --> loop device --> mounted EXT3 filesystem
The problem is that in the past, "umount /dev/loop4" worked, and this is the command that the Gnome interface is executing.
My setup is as follows:
daniel@elvandar:~$ dpkg -S /bin/umount
diversion by loop-aes-utils from: /bin/umount
diversion by loop-aes-utils to: /bin/umount.orig
mount, loop-aes-utils: /bin/umount
daniel@elvandar:~$ dpkg -l mount loop-aes-utils
||/ Name Version Description ======= ====-== ======= =====-= ======= ======= ======= ======= ======= ======= =
+++-===
ii loop-aes-utils 2.12r-11 Tools for mounting and manipulating filesyst
ii mount 2.12r-11ubuntu Tools for mounting and manipulating filesyst
So, perhaps the problem is loop-aes-utils?