From: Jeff Layton Subject: Re: lockd not responding Date: Sat, 22 Sep 2007 17:31:05 -0400 Message-ID: <20070922173105.5b2607f5.jlayton@redhat.com> References: <20070912202721.d8f70ac1.jlayton@redhat.com> <1190407932.6721.42.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: kenneth johansson , nfs@lists.sourceforge.net To: Trond Myklebust Return-path: Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IZCZw-0006wv-EC for nfs@lists.sourceforge.net; Sat, 22 Sep 2007 14:31:57 -0700 Received: from mx1.redhat.com ([66.187.233.31]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IZCa0-0002FF-4r for nfs@lists.sourceforge.net; Sat, 22 Sep 2007 14:32:01 -0700 In-Reply-To: <1190407932.6721.42.camel@heimdal.trondhjem.org> List-Id: "Discussion of NFS under Linux development, interoperability, and testing." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfs-bounces@lists.sourceforge.net Errors-To: nfs-bounces@lists.sourceforge.net On Fri, 21 Sep 2007 16:52:12 -0400 Trond Myklebust 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 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 ------------------------------------------------------------------------- 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