> To avoid a misunderstanding: Which protocol timeout do you mean? It is
> the -timeo=n option? (Even tried without success)
I was referring to the built-in protocol timeouts; but if you're using UDP
rather than TCP, I guess there's no built-in timeout at all. However, the
nfs(5) manpage lists this option which governs how long mount will wait for
an NFS mount to succeed:
retry=n The number of minutes that the mount(8) command retries
an NFS mount operation in the foreground or background
before giving up. If this option is not specified, the
default value for foreground mounts is 2 minutes, and
the default value for background mounts is 10000 minutes
(80 minutes shy of one week).
So you can use that option to override.
As for the "no route to host" being returned immediately: I had been
assuming that you *did* have a route to the host and that the mount was
timing out simply because it was getting no response from the network.
However, I did a quick test here by removing my default route and
attempting to mount an NFS filesystem from a randomly chosen unroutable
IP. I can confirm that the mount command waits, presumably in a retry
loop, instead of exiting immediately.
Since this retry happens at the kernel level, I'm reassigning this to
the kernel package.
** Package changed: nfs-utils (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
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
