Ross Vandegrift wrote: > On Thu, Jun 25, 2009 at 05:32:14PM +0200, Michael Biebl wrote: >> Ross Vandegrift wrote: >>> Package: gnome-mount >>> Version: 0.8-2 >>> Severity: important >>> >>> >>> Hello, after updating my squeeze installation, I am no longer able to >>> umount USB devices using gnome-mount. If I attach my USB device, >>> nautilus automounts the device just fine. >>> >>> However, when I try to unmount the device, gnome-mount responds: >>> "An application is preventing the volume 'COWON' from being >>> unmounted." >>> >>> But there are no processes with open fds on the volume: >>> >>> rvandegr...@malaclypse:~$ sudo fuser -m /media/COWON/ >>> rvandegr...@malaclypse:~$ >>> >>> If I log out of my X session, and SSH in remotely, I can sucessfully run >>> "gnome-mount --unmount --device /dev/sdb1" and it correcly unmounts the >>> device. >> Then there was a process blocking the umount. Did you also check with lsof? >> >> Imho not a bug in gnome-mount. Just try to find the process. > > I just checked that. lsof finds no open files under /media/COWON (the > mountpoint in question): > malaclypse:~# lsof +D /media/COWON/ > malaclypse:~# > > Checking the open fd links in /proc also shows that there are no > processes keeping such files open: > > malaclypse:/proc# ls -l /proc/*/fd/* | grep COWON > ls: cannot access /proc/3150/fd/255: No such file or directory > ls: cannot access /proc/3150/fd/3: No such file or directory > ls: cannot access /proc/3151/fd/255: No such file or directory > ls: cannot access /proc/3151/fd/3: No such file or directory > ls: cannot access /proc/self/fd/255: No such file or directory > ls: cannot access /proc/self/fd/3: No such file or directory > malaclypse:/proc#
Not sure, but maybe gnome-vfs/gvfs/fuse/nautilus is blocking the umount. You could try to kill the processes step by step to find the culprit. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
