I have the same problem. In my case the server is a SAMBA server
running under Linux, and the client is a laptop running an up-to-date
Ubuntu "hardy". Several SMB partitions are mounted on my laptop via
automount, for example:
$ cat /etc/auto.freak
# ...
pictures -fstype=nfs,nosuid,nodev,intr freak:/home/pictures
The server "freak" is at home, unreachable from the internet. When I am
at work and try to open a nautilus window, it takes ages (multiple
minutes). If I connect an strace to the nautilus process, I see system
calls like the following:
access("/freak/pictures/incoming/canon", F_OK) = -1 ENOENT (No such file or
directory)
access("/freak/pictures/incoming/canon", F_OK) = -1 ENOENT (No such file or
directory)
access("/freak/pictures/incoming/canon", F_OK) = -1 ENOENT (No such file or
directory)
each one taking about 30 seconds to time out. This is the case even if
the directory that I am opening with nautilus is on a locally-mounted
partition. The directories that are being sought are directories that I
have recently accessed using nautilus while at home (i.e., while those
SMB shares were accessible). During this time, the automounted
partitions are *not* mounted (as determined from the "mount" command).
The long delays make nautilus nearly useless. I hope this information
helps diagnose the problem. Let me know if I can help you with any more
information.
--
Shutting down server causes Nautilus to slow down on Remote Ubuntu clients
(SAMBA CIFS)
https://bugs.launchpad.net/bugs/134752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
