[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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
[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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
[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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
[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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
[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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
[Bug 234480] [NEW] autofs hangs when server unavailable
Public bug reported: 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: -Hardy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.24-16-386 #1 Thu Apr 10 12:50:06 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ 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://mirror.aarnet.edu.au hardy-updates/main Packages 100 /var/lib/dpkg/status 1:1.1.2-2ubuntu2 0 500 http://mirror.aarnet.edu.au hardy/main Packages [EMAIL PROTECTED]:~$ 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 real0m40.128s user0m0.028s sys 0m0.000s ---Gutsy--- [EMAIL PROTECTED]:~$ cat /etc/*-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" [EMAIL PROTECTED]:~$ uname -a Linux client 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED]:~$ apt-cache policy nfs-common nfs-common: Installed: 1:1.1.1~git-20070709-3ubuntu1 Candidate: 1:1.1.1~git-20070709-3ubuntu1 Version table: *** 1:1.1.1~git-20070709-3ubuntu1 0 500 http://au.archive.ubuntu.com gutsy/main Packages 100 /var/lib/dpkg/status [EMAIL PROTECTED]:~$ 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 real0m3.006s user0m0.000s sys 0m0.004s - ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New -- autofs hangs when server unavailable https://bugs.launchpad.net/bugs/234480 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