From: Jeff Layton <jtlayton@poochiereds.net>
Subject: Re: Breaking locks on a lame server?
Date: Wed, 03 May 2006 10:33:00 -0400
Message-ID: <1146666780.5635.10.camel@tleilax.poochiereds.net>
References: <445820B0.8080107@temple-baptist.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: nfs@lists.sourceforge.net
To: Erik Walthinsen <omega@temple-baptist.com>
In-Reply-To: <445820B0.8080107@temple-baptist.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

On Tue, 2006-05-02 at 20:17 -0700, Erik Walthinsen wrote:
> 1) am I to expect 2.6's NFS server implementation to somehow solve this?
> 2) if not, and in the meantime, are there any means by which I can inspect 
> (lslk does nothing) and hopefully kill these locks?

One thing you can do (ableit not a nice thing), is to send a SIGKILL to
lockd on the NFS server. This will make it drop all of its locks.
Restarting statd just afterward should cue the active clients to
reacquire them. This has races, but may be better than restarting your
NAS. This works with 2.4 and 2.6 kernels.

I also recently posted a patch to add a procfs interface that would
allow dropping of locks on just a single block device (mostly to help in
clustered situations), but I received no comment on it. Depending on
your setup, that may help you as well.

-- Jeff


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs