Kip, with v3 TCP mounts I'm getting:
Stale NFS file handle. complaints after a few hours of inactivity. I've verified that the filer has not rebooted. Adi On Fri, Apr 05, 2002 at 11:19:39PM -0800, Kip Macy wrote: > > Okay, I've forced nfs v3 and tcp like this: > > > > -3,tcp,ro,intr,nodev,nosuid,noauto > > > > and seems to work fine too...so the problem is with fragments on v2 and v3 UDP > > mounts (I tested both and they had the same "hanging" behaviour). > > > > I'm glad that that fixed the problem. If this is not already documented on this > end, I will try to get it updated to reflect this. > > I think TCP should be the default. I agree with Kirk that the designers of > NFSv2 took statelessness a little too seriously when they used UDP. The fact of > the matter is you still have state, but you move it from the network stack into > the client and the server. The end effect being that you reproduce parts of TCP > badly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
