Given that this bug has hung around for a couple of years without much action, I thought I would have another dig around to see if I could find anything useful.
I eventually came to the conclusion that this is actually a kernel issue. It seems that the Gutsy kernel (2.6.22) returns immediately with a "No route to host" message when the server is unavailable, while the later kernels return after a significant delay with alternative error messages.
Given that this bug has hung around for a couple of years without much action, I thought I would have another dig around to see if I could find anything useful.
I eventually came to the conclusion that this is actually a kernel issue. It seems that the Gutsy kernel (2.6.22) returns immediately with a "No route to host" message when the server is unavailable, while the later kernels return after a significant delay with alternative error messages.
I also found this post: http:// linux-nfs. org/pipermail/ nfsv4/2010- February/ 012112. html that discusses this issue. It indicates that we might see some improvement in kernel 2.6.33.