Hello Steve, thanks for your immediate answer: > [...] If the server is down, then > your client has no way to *know* that the server is down, except by > waiting for the protocol timeout to be reached. > [...] > To avoid a misunderstanding: Which protocol timeout do you mean? It is the -timeo=n option? (Even tried without success)
An example for (3.) scenario 1: A) On my openSuSE 11.1 Desktop (linux nfs-utils 1.1.3, ifup-configured) I get "No route to host" after 3 seconds (which is OK): time mount.nfs 192.168.2.12:/exports /tmp/test -v mount.nfs: timeout set for Mon Nov 2 23:02:58 2009 mount.nfs: text-based options: 'addr=192.168.2.12' mount.nfs: Unable to connect to 192.168.2.12:111, errno 113 (No route to host) mount.nfs: mount to NFS server '192.168.2.12:/exports' failed: System Error: No route to host real 0m3.005s user 0m0.000s sys 0m0.004s B) on my Ubuntu 9.10 Notebook (linux nfs-utils 1.1.6, networkmanager-configured) I get an "Input/output error" after 60 seconds (which is too long) time mount.nfs 192.168.2.12:/exports /tmp/test -v mount.nfs: timeout set for Mon Nov 2 23:14:46 2009 mount.nfs: text-based options: 'addr=192.168.2.12' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed real 1m0.004s user 0m0.004s sys 0m0.000s Same with Jaunty. All machines have fix IP adresses. It is easy to reproduce: Just create the mount point and use a not-reachable IP adress for the NFS server. How can the protocol timeout you mentioned above be set? -- mount.nfs hangs when nfs server is not reachable https://bugs.launchpad.net/bugs/470405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
