On 03/10/2010 04:42 PM, Chuck Lever wrote: > Currently if a server is up but not responding (ie, it answers ARP > requests, but not NFS or RPC requests), mount retries or backgrounds > itself waiting for the server. > > If the server is not responding on the network at all, mount fails > the mount request immediately. > > Users might find it more useful if mount retried in both cases. > > Note that this change means attempting to mount using a misspelled > server name will "hang" for the retry amount. I suppose the error > message isn't very helpful whether it fails immediately or waits > a couple of minutes, though I imagine that an unreachable server is a > much more common occurrence than a misspelling. > > Reported-by: Daniel Goering <g_daniel@xxxxxxx> > Signed-off-by: Chuck Lever <chuck.lever@xxxxxxxxxx> > --- Committed... steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
