autofs hangs when server unavailable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nfs-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: nfs-common
When using autofs in Hardy to automount nfs shares, lengthy hangs occur if the target server is not available. This causes nautilus (and the desktop) to hang at login and when opening. The problem seems to originate with changed behaviour of mount.nfs. When attempting to mount a non-existent server export, Gutsy returns in about 3 seconds with the "No route to host" message, Hardy takes about 40 seconds and returns an "internal error". This results in lengthy delays if there are multiple autofs connections to be attempted. These behaviours are shown below:
-------
me@client:~$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
me@client:~$ uname -a
Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux
me@client:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.1.2-2ubuntu2.1
Candidate: 1:1.1.2-2ubuntu2.1
Version table:
*** 1:1.1.2-2ubuntu2.1 0
500 http://
100 /var/lib/
1:
500 http://
me@client:~$ time sudo mount.nfs server:/media/share /media/test -v
[sudo] password for me:
mount.nfs: timeout set for Sat May 24 09:51:29 2008
mount.nfs: text-based options: 'addr=192.168.0.99'
mount.nfs: internal error
real 0m40.128s
user 0m0.028s
sys 0m0.000s
-------
me@client:~$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_
DISTRIB_
DISTRIB_
me@client:~$ uname -a
Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
me@client:~$ apt-cache policy nfs-common
nfs-common:
Installed: 1:1.1.1~
Candidate: 1:1.1.1~
Version table:
*** 1:1.1.1~
500 http://
100 /var/lib/
me@client:~$ time sudo mount.nfs server:/media/share /media/test/ -v
[sudo] password for me:
mount.nfs: Unable to connect to 192.168.0.99:111, errno 113 (No route to host)
mount.nfs: mount to NFS server 'compaq' failed: System Error: No route to host
real 0m3.006s
user 0m0.000s
sys 0m0.004s
-------
this bugs seems related to bug #214041