On a machine I use I have some NFS mounts that access huge
amounts (terabytes) of filesystem space. I installed Nautilus
for the first time on this machine and started it up. The
"Searching for Trash folders" dialog came up and stayed up
for several minutes. I also noticed continuous activity on
the ethernet interface. Some poking around with lsof showed
that nautilus was walking the remoted mounted (NFS) filesystems.


* REPRODUCIBLE: Always

* STEPS TO REPRODUCE:

(I assume I could repro this everytime, but I just tried once).

NFS mount some huge filesystems.

Start nautilus.


* EXPECTED RESULTS: 

  I think the "Searching for Trash folders" operation should only
walk local filesystems. Or at least be configurable like medusa
is via a "stoplist".



------- Additional Comments From darin@bentspoon.com 2001-02-01 10:46:47 ----

It's high priority to at least decide what do do about this.



------- Additional Comments From liblit@acm.org 2001-02-12 01:07:07 ----

It gets worse.

My box (which is at a large University) uses automount maps where each user's
home directory is its own mount map key and therefore its own NFS mount point. 
Near as I can tell, Nautilus's actions result in *every* user's home directory
being mounted.  (Or at least, every such directory that my workstation has
permission to mount.)

This creates a rather extreme burst of mount activity on both the NFS client and
NFS server end of things.  A similar burst of unmount activity comes a few
minutes later when the automounter decides to expire everything.  That one
actually makes my mouse jerky for several seconds.

To be honest, I'm just speculating that this is the same issue.  It might be
different, in which case I'll happily file a new bug report.  The main issue I'm
seeing is that starting Nautilus causes spontaneous automounting of all (many?)
users' home directories.



------- Additional Comments From liblit@acm.org 2001-02-15 18:09:21 ----

I'm going to go ahead and file the automounter issue as a new bug.  Walking
though mounted NFS volumes is really a distinct issue from causing automatic
mounting of NFS volumes that were not already mounted.



------- Additional Comments From gzr@eazel.com 2001-02-22 02:48:25 ----

I added code in the volume monitor where automount entries should be ignored 
and not mounted, thereby makin gthem inaccesible to the trash code. Did this 
help any?



------- Additional Comments From bdodd@jump.net 2001-03-13 13:03:54 ----

This problem still exists in 1.0. i.e. The "searching for trash folders" 
is still walking through all my mounted NFS filesystems. The comment
from gzr makes me think something was done to prevent automount
entries from being mounted, but I can't verify this since I don't
do automounts.

I still think there should be an option to have the trash folder searching
code walk local filesystems only. 





------- Additional Comments From eli@eazel.com 2001-03-26 11:20:00 ----

SPAAAAAAAAAM! 

(Jon Allen has taken these components; QA Assigning bugs to him.)



------- Additional Comments From don@eazel.com 2001-04-11 14:19:19 ----

This is not a 1.0.3 requirment, but I would like to fix this sometime soon.




------- Additional Comments From snickell@stanford.edu 2001-07-23 00:33:32 ----

Taking bugs previously assigned to Pavel, assigning them to myself. Will parse
them out at my leisure , but many are GnomeVFS bugs we should look at for 2.0



------- Additional Comments From mjs@noisehavoc.org 2001-07-23 01:17:03 ----

Move to unassigned. I'll probably want to take a crack at some of these myself,
and Seth says he is unlikely to.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:58 -------

The original reporter (bdodd@jump.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.