Date: Sat, 6 Apr 2002 10:33:10 -0800 From: Aditya <aditya@grot.org> To: Kip Macy <kmacy@netapp.com> Cc: freebsd-stable@freebsd.org Subject: Re: NFS hang with fxp and Network Appliance fileserver Message-ID: <20020406183310.GA10055@mighty.grot.org> In-Reply-To: <Pine.GSO.4.10.10204052259090.20180-100000@orbit> References: <20020406055443.GA82908@mighty.grot.org> <Pine.GSO.4.10.10204052259090.20180-100000@orbit>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020406183310.GA10055>