GNOME Bugzilla – Bug 94552
famd prevents nautilus from unmounting removable devices
Last modified: 2005-02-03 20:56:20 UTC
I have a DVD-RAM drive formated as vfat and mounted via mount -t auto -o umask=000 /dev/cdrom /mnt/dvd If I then access the drive via the Nautilus file tree and issue umount /mnt/dvd , I get the message: device is busy. Clicking other parts of the file tree does not help. I continue to get the message until I close the Nautilus window. I believe that Redhat 7.3 comes with Gnome2, but I was unable to verify this.
this is generic for any removable *writable* devices. For example USB/Firewire harddisks, my Sony Clie which exports its memory stick as a usb-storage device.. The problem is with FAM: umount /mnt/clie umount: /mnt/clie: device is busy and: # lsof /mnt/clie COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME famd 830 root 157r DIR 8,1 16384 2 /mnt/clie/.Trash-tigert I think this has been reported earlier too but I couldnt find the bug number right now :-/ sorry about that. Has anyone looked into this, it makes mounting stuff and using them with nautilus such a pain - *even* if you dont browse the device with nautilus, since the moment you mount it if it is user mountable, it pops on the desktop and FAM hooks into it, not freeing the "watch" so the kernel fails to umount the device. This plainly sucks and makes it painful to use, I need to su root; killall famd; killall nautilus *every* time I need to umount my firewire disk for example - causes me to lose my work setup on the open nautilus windows etc..
*** Bug 127426 has been marked as a duplicate of this bug. ***
Are you using fam in standalone or inetd mode ? If you're using the inetd one could you try with standalone, fam seems to have some problems with the inetd mode ...
*** Bug 146420 has been marked as a duplicate of this bug. ***
*** Bug 141049 has been marked as a duplicate of this bug. ***
I've changed the bug title to better describe what's going on here.
*** This bug has been marked as a duplicate of 102760 ***
*** Bug 166176 has been marked as a duplicate of this bug. ***