From: Neil Brown <neilb@suse.de>
To: cluster-devel.redhat.com
Subject: [NFS] [Cluster-devel] [PATCH 0/4 Revised] NLM - lock failover
Date: Fri, 27 Apr 2007 22:40:16 +1000 [thread overview]
Message-ID: <17969.61232.323762.29003@notabene.brown> (raw)
In-Reply-To: <message from Jeff Layton on Friday April 27>
On Friday April 27, jlayton at 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
WARNING: multiple messages have this Message-ID (diff)
From: Neil Brown <neilb@suse.de>
To: Jeff Layton <jlayton@poochiereds.net>
Cc: cluster-devel@redhat.com, nfs@lists.sourceforge.net
Subject: Re: [Cluster-devel] [PATCH 0/4 Revised] NLM - lock failover
Date: Fri, 27 Apr 2007 22:40:16 +1000 [thread overview]
Message-ID: <17969.61232.323762.29003@notabene.brown> (raw)
In-Reply-To: message from Jeff Layton on Friday April 27
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
next prev parent reply other threads:[~2007-04-27 12:40 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 21:50 [Cluster-devel] [PATCH 0/4 Revised] NLM - lock failover Wendy Cheng
2007-04-05 21:50 ` Wendy Cheng
2007-04-11 17:01 ` [Cluster-devel] Re: [NFS] " J. Bruce Fields
2007-04-11 17:01 ` J. Bruce Fields
2007-04-17 19:30 ` [Cluster-devel] " Wendy Cheng
2007-04-17 19:30 ` Wendy Cheng
2007-04-18 18:56 ` [Cluster-devel] " Wendy Cheng
2007-04-18 18:56 ` Wendy Cheng
2007-04-18 19:46 ` [Cluster-devel] " Wendy Cheng
2007-04-18 19:46 ` Wendy Cheng
2007-04-19 14:41 ` [Cluster-devel] Re: [NFS] " Christoph Hellwig
2007-04-19 14:41 ` Christoph Hellwig
2007-04-19 15:08 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-19 15:08 ` Wendy Cheng
[not found] ` <message from Wendy Cheng on Tuesday April 17>
2007-04-19 7:04 ` [Cluster-devel] " Neil Brown
2007-04-19 7:04 ` Neil Brown
2007-04-19 14:53 ` Wendy Cheng
2007-04-19 14:53 ` Wendy Cheng
2007-04-24 3:30 ` Wendy Cheng
2007-04-24 3:30 ` Wendy Cheng
[not found] ` <message from Wendy Cheng on Monday April 23>
2007-04-24 5:52 ` [NFS] " Neil Brown
2007-04-24 5:52 ` Neil Brown
2007-04-26 4:35 ` [NFS] " Wendy Cheng
2007-04-26 4:35 ` Wendy Cheng
[not found] ` <message from Wendy Cheng on Thursday April 26>
2007-04-26 5:43 ` [NFS] " Neil Brown
2007-04-26 5:43 ` Neil Brown
2007-04-27 2:24 ` [NFS] " Wendy Cheng
2007-04-27 2:24 ` Wendy Cheng
2007-04-27 6:00 ` [NFS] " Neil Brown
2007-04-27 6:00 ` Neil Brown
2007-04-27 11:15 ` [NFS] " Jeff Layton
2007-04-27 11:15 ` Jeff Layton
[not found] ` <message from Jeff Layton on Friday April 27>
2007-04-27 12:40 ` Neil Brown [this message]
2007-04-27 12:40 ` Neil Brown
2007-04-27 13:42 ` Jeff Layton
2007-04-27 18:57 ` [NFS] " Jeff Layton
2007-04-27 14:17 ` Christoph Hellwig
2007-04-27 14:17 ` Christoph Hellwig
2007-04-27 15:42 ` J. Bruce Fields
2007-04-27 15:43 ` [NFS] " J. Bruce Fields
2007-04-27 15:36 ` Wendy Cheng
2007-04-27 15:36 ` Wendy Cheng
2007-04-27 16:31 ` J. Bruce Fields
2007-04-27 16:31 ` [NFS] " J. Bruce Fields
[not found] ` <message from J. Bruce Fields on Friday April 27>
2007-04-27 22:22 ` Neil Brown
2007-04-27 22:22 ` Neil Brown
2007-04-29 20:13 ` J. Bruce Fields
2007-04-29 20:14 ` [NFS] " J. Bruce Fields
[not found] ` <message from J. Bruce Fields on Sunday April 29>
2007-04-29 23:10 ` Neil Brown
2007-04-29 23:10 ` Neil Brown
2007-04-30 5:19 ` [NFS] " Wendy Cheng
2007-04-30 5:19 ` Wendy Cheng
2007-05-04 18:42 ` [NFS] " J. Bruce Fields
2007-05-04 18:42 ` J. Bruce Fields
2007-05-04 21:35 ` [NFS] " Wendy Cheng
2007-05-04 21:35 ` Wendy Cheng
2007-04-27 20:34 ` Frank van Maarseveen
2007-04-27 20:34 ` [NFS] " Frank van Maarseveen
2007-04-28 3:55 ` Wendy Cheng
2007-04-28 3:55 ` Wendy Cheng
[not found] ` <message from Wendy Cheng on Friday April 27>
2007-04-28 4:51 ` [NFS] " Neil Brown
2007-04-28 4:51 ` Neil Brown
2007-04-28 5:26 ` Marc Eshel
2007-04-28 5:27 ` [NFS] " Marc Eshel
2007-04-28 12:33 ` Frank van Maarseveen
2007-04-28 12:33 ` [NFS] " Frank van Maarseveen
2007-04-27 15:12 ` Jeff Layton
2007-04-27 15:12 ` [NFS] " Jeff Layton
2007-04-25 14:18 ` [Cluster-devel] Re: [NFS] " J. Bruce Fields
2007-04-25 14:18 ` J. Bruce Fields
2007-04-25 14:10 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-25 14:10 ` Wendy Cheng
2007-04-25 15:21 ` [Cluster-devel] Re: [NFS] " Marc Eshel
2007-04-25 15:21 ` Marc Eshel
2007-04-25 15:19 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-25 15:19 ` Wendy Cheng
2007-04-25 15:39 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-25 15:39 ` [Cluster-devel] " Wendy Cheng
2007-04-25 15:59 ` [Cluster-devel] Re: [NFS] " J. Bruce Fields
2007-04-25 15:59 ` J. Bruce Fields
2007-04-25 15:52 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2007-04-25 15:52 ` Wendy Cheng
2011-11-30 10:13 ` Pavel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17969.61232.323762.29003@notabene.brown \
--to=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.