On 07/16/10 12:10 PM, Tom H wrote:
Chuck Lever wrote:
On 07/16/2010 11:20 AM, Tom H wrote:
(also I noticed that it seems to timeout quicker with the mount options
set like (soft, timeo=7, retrans=3) which is unexpected, because they
are supposed to be the default)
They are the default settings for UDP mounts, but you didn't specify
UDP. TCP is the default transport protocol, and has been for some
time. TCP uses a long retransmit timeout. See nfs(5).
OK, I see that now. Thanks.!
However further experimentation with mount options
(ro,soft,retrans=0,timeo=0,intr,proto=tcp) - requests to a failed nfs
file-system still block the apache process for some apparently random
time up to 3 minutes.
I don't know exactly what retrans=0 and timeo=0 might do, but short
timeouts over TCP are not recommended. If you want it to fail sooner
(and your network is clean enough), use proto=udp.
--
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
