From: Jeff Layton Subject: Re: lockd not responding Date: Wed, 12 Sep 2007 20:27:21 -0400 Message-ID: <20070912202721.d8f70ac1.jlayton@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: nfs@lists.sourceforge.net To: kenneth johansson Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list2-new.sourceforge.net with esmtp (Exim 4.43) id 1IVcYK-0002Rb-29 for nfs@lists.sourceforge.net; Wed, 12 Sep 2007 17:27:28 -0700 Received: from mx1.redhat.com ([66.187.233.31]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1IVcYO-0006wN-Jq for nfs@lists.sourceforge.net; Wed, 12 Sep 2007 17:27:32 -0700 In-Reply-To: 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 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... -- 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