After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 81079 - Nautilus can not unmount NFS mounted files.
Nautilus can not unmount NFS mounted files.
Status: RESOLVED DUPLICATE of bug 84919
Product: nautilus
Classification: Core
Component: Navigation
1.0.x
Other other
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-07 19:30 UTC by kpratt
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 1.4


Description kpratt 2002-05-07 19:30:28 UTC 
Package: nautilus
Severity: major
Version: 1.0.6
Synopsis: Nautilus can not unmount NFS mounted files.
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation

Description:
When I use the (right click)->Disks to mount an NFS volume then attempt
to unmount that volume, most of the time I receive an error message
stating that the device is busy.

When I use fuser to inspect what process has the share open, I get
nothing back.  What is keeping the mount point busy so that I can not
unmount?




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-05-07 15:30 -------

Unknown version 1.0.x in product nautilus. Setting version to the default, "unspecified".
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 John Fleck 2002-05-11 12:35:59 UTC 
It'd be great to know if this is an issue on GNOM2 Nautilus.
Comment 2 Luis Villa 2002-05-12 22:58:28 UTC 
I used to almost never be able to do this in nautilus1 but it works
for me most of the time now.
Comment 3 Tuomas Kuosmanen 2002-05-31 17:06:59 UTC 
Howdy Luis ;-)

So this happens with my firewire disk too. Not *every* time, but often
enough to be annoying. WHEN it says "device is busy", one of the
options is naturally that it is really busy - meaning you have a shell
open or something. I dont know if we can do much about that, since
only root can force-umount stuff.

But the real problem here seems to be FAM - whenever I do a "lsof
/mnt/fwdisk" (note, no trailing slash, otherwise it returns empty!) I
get this: 

COMMAND PID USER   FD   TYPE DEVICE SIZE NODE NAME
famd    626 root   26r   DIR    8,2 4096    2 /mnt/fwdisk/.Trash-tigert

Meaning FAM is monitoring the TRASH on that volume. Now, that would be
one thing to take care of, if nautilus is about to umount a volume, it
would definitely make sense to tell FAM to stop that.
Comment 4 Luis Villa 2002-06-26 01:10:21 UTC 

*** This bug has been marked as a duplicate of 84919 ***