From: Neil Brown Subject: Re: [Cluster-devel] [PATCH 0/4 Revised] NLM - lock failover Date: Fri, 27 Apr 2007 22:40:16 +1000 Message-ID: <17969.61232.323762.29003@notabene.brown> References: <46156F3F.3070606@redhat.com> <4625204D.1030509@redhat.com> <17959.5245.635902.823441@notabene.brown> <462D79F0.4060800@redhat.com> <17965.39683.396108.623418@notabene.brown> <46302C01.2060500@redhat.com> <17968.15370.88587.653447@notabene.brown> <46315EED.9020103@redhat.com> <17969.37229.250000.895316@notabene.brown> <20070427111513.GA25126@salusa.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: cluster-devel@redhat.com, nfs@lists.sourceforge.net To: Jeff Layton 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 1HhPkg-00079J-Ri for nfs@lists.sourceforge.net; Fri, 27 Apr 2007 05:40:47 -0700 Received: from mx2.suse.de ([195.135.220.15]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1HhPkf-0003pn-1R for nfs@lists.sourceforge.net; Fri, 27 Apr 2007 05:40:45 -0700 In-Reply-To: message from Jeff Layton on Friday April 27 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 Friday April 27, jlayton@poochiereds.net wrote: > On Fri, Apr 27, 2007 at 04:00:13PM +1000, Neil Brown wrote: > > > > So if you need that, then I think it really must be implemented by > > something a lot like > > echo -n /path/name > /proc/fs/nfs/nlm_unlock_filesystem > > > > This is something that we could possible teach "fuser -k" about - so > > it can effectively 'kill' that part of lockd that is accessing a given > > filesystem. It is useful to failover, but definitely useful beyond > > failover. > > Just a note that I posted a patch ~ a year ago that did precisely that. The > interface was a little bit different. I had userspace echoing in a dev_t > number, but it wouldn't be too hard to change it to use a pathname instead. > > Subject was: > > [PATCH] lockd: add procfs control to cue lockd to release all locks on a device > > ...if anyone is interested in having me resurrect it. > > -- Jeff http://lkml.org/lkml/2006/4/10/240 Looks like no-one ever replied. I probably didn't see it: things on linux-kernel that don't have 'nfs' or 'raid' (or a few related strings) in the subject have at best an even chance of me seeing them. I've just added 'lockd' to the list of important strings :-) I would rather a path name, and would rather it came through the 'nfsd' filesystem, but those are fairly trivial changes. nlm_traverse_files has changed a bit since then, but it should be easier to unlock based on filesystem with the current code (especially if we made the first arg a void*..). NeilBrown ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs