Re: lockd not responding

[Jeff Layton <jlayton@redhat.com>]

On Fri, 21 Sep 2007 16:52:12 -0400
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:

> On Wed, 2007-09-12 at 20:27 -0400, Jeff Layton wrote:
> > On Wed, 12 Sep 2007 07:26:02 +0000 (UTC)
> > kenneth johansson <ken@kenjo.org> wrote:
> > 
> > > Got a warning from the lock validating check again and
> > > later a unresponsive lockd with a backtrace this time
> > > actually at the same place the lock warning was on.
> > 
> > FWIW, I think I ran into the exact same problem recently. I opened a
> > BZ case for it so I wouldn't forget about it, but haven't had time to
> > track it down:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=280311
> > 
> > I'm not certain that lockd was stuck at the time, since I had some
> > other things going on with the box, but it may have been...
> 
> Does the attached patch help?
> 
> Cheers
>   Trond
> 

Thanks, Trond -- nice work :-)

Yes. It does seem to. I have a reproducer of sorts -- run this in a
continuous loop:

lock file
sleep 2 seconds
unlock file
sleep 1 second

When run simultaneously on the server and client against the same
inode, the lockdep warning usually pops within a few minutes. With
the patch above, I never saw it, even after running for 20 mins or
so.

-- 
Jeff Layton <jlayton@redhat.com>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs