Date: Tue, 15 Aug 2006 19:49:10 +0800 From: "Rong-en Fan" <grafan@gmail.com> To: "Kris Kennaway" <kris@obsecurity.org>, "Morten A. Middelthon" <morten@freenix.no> Cc: stable@freebsd.org Subject: Re: NFS locking question Message-ID: <6eb82e0608150449p3320b5eeu2b731fec42de9218@mail.gmail.com> In-Reply-To: <20060815101114.GA51674@xor.obsecurity.org> References: <20060228101453.GB47953@hugo10.ka.punkt.de> <20060228102150.GA56625@xor.obsecurity.org> <20060815095950.GD34840@freenix.no> <20060815101114.GA51674@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/15/06, Kris Kennaway <kris@obsecurity.org> wrote: > On Tue, Aug 15, 2006 at 11:59:50AM +0200, Morten A. Middelthon wrote: > > On Tue, Feb 28, 2006 at 05:21:50AM -0500, Kris Kennaway wrote: > > > On Tue, Feb 28, 2006 at 11:14:53AM +0100, Patrick M. Hausen wrote: > > > > Hi, all! > > > > > > > > In our local office network we have a rather old FreeBSD 5.2.1 > > > > server acting as an NFS server for several other systems, mostly > > > > running 6.0. > > > > > > > > >From time to time we experience processes on the NFS clients > > > > hanging in statd "D" with wchan "lockd" when accessing files > > > > over NFS. > > > > > > Try the attached patch on the 6.0 machines: > > > > > > Index: usr.sbin/rpc.lockd/lock_proc.c > > <snip> > > > > Hi, > > > > I have been plagued with this NFS lockd issue for quite some time now. It has > > kept me from installing FreeBSD 6.x on our workstations at work. I just tried > > applying your patch to my own 6.1-RELEASE-p3 workstation, and so far it has > > been working nicely. Has anyone else had the same experience? If so, maybe it > > should go into production? > > I was unable to obtain confirmation from anyone else (including the > submitter who previously claimed it was necessary, and my own testing) > that the patch actually solved a problem. Since it involves reverting > useful functionality, someone would need to obtain further debugging > from your system (tcpdump traces before/after, etc) to determine what > it's actually solving. > > Kris In my experiences, rpc.lockd dies automatically on both server and client. If this happens, then all processes that want to lock a file, they will be stuck in lockd (top will tell). In my case, rpc.lockd dies because write failed, and then a SIGPIPE generated. Two months ago, bin/97768 is sent and rodrigc@ committed (also MFC'ed in RELENG_6). That PR ignores SIGPIPE (since the code in server/client already takes care of write failed case). After I applied this PR, I'm quite happy with nfs locking. Regards, Rong-En Fan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0608150449p3320b5eeu2b731fec42de9218>