Date: Mon, 1 Jun 1998 18:17:15 -0500 (CDT) From: Kevin Day <toasty@home.dragondata.com> To: tlambert@primenet.com (Terry Lambert) Cc: mi@video-collage.com, current@FreeBSD.ORG Subject: Re: NFS discovery Message-ID: <199806012317.SAA20375@home.dragondata.com> In-Reply-To: <199806012302.QAA28930@usr05.primenet.com> from Terry Lambert at "Jun 1, 98 11:02:36 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > > NFS hung ups are a strange topic, in my experience. People agree > > > that they are "bad", but one is not supposed to complain about > > > them... > > > > Don't read my post as a complaint, rather as a 'hey, why does it do this?" > > :) > > > The freeze on server crash comes from an outstanding RPC call that > was made, the call was ack'ed, but the response had not yet been sent. > > Because the call was ack'ed, the client doesn't retry the call. > This is arguably a bug in the client code. > > The easiest workaround is to use UDP NFS instead of TCP. I am using UDP.... (TCP seemed much much worse) I'm resigned to the fact that NFS does freeze and never come back... What I was curious about was why the `mount -u -o async /blah` 'unfroze' it. I am going to reboot the server tonight, and I'm going to try to keep the client up. If there's anything anyone wants me to do (other than check to see what all the processes are waiting on) please let me know within a few hours. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806012317.SAA20375>