From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: lockd crash
Date: Thu, 18 Oct 2007 11:15:55 -0400
Message-ID: <1192720555.7437.13.camel@heimdal.trondhjem.org>
References: <Pine.LNX.4.62.0710181511090.759@office2.c1.internal>
	<1192718684.7437.3.camel@heimdal.trondhjem.org>
	<Pine.LNX.4.62.0710181707440.6931@office2.c1.internal>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Allard Hoeve <allard@byte.nl>
In-Reply-To: <Pine.LNX.4.62.0710181707440.6931@office2.c1.internal>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net


On Thu, 2007-10-18 at 17:09 +0200, Allard Hoeve wrote:
> Hello Trond, all,
> 
> >> We've been experincing strange lockd crashes on one of our file servers
> >> lately. The kernel lockd gets stuck in a D state and is unkillable, while
> >> other NFS processes continue to work fine. Files are served, we're able to
> >> mount/umount etc, but trying to attain a lock results in a (killable with
> >> KILL) process on the client.
> >
> > http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc7/linux-2.6.23-001-fix_lockd_circular_dependency.dif
> 
> Thanks for the link.
> 
> Is it feasible to backport this to, say 2.6.20?
> 
> Otherwise, I'll have to find a way to upgrade to 2.6.23, which is a bit 
> too new to my tastes :)
> 
> Regards,
> 
> Allard Hoeve

It is already queued for the 2.6.22 stable series (in fact it may
already be in the last tarball).

It should be fairly trivial to backport both to 2.6.20 and 2.6.17...

Trond


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs