From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 1/4 Revised] NLM - drop per fsid locks
Date: Mon, 9 Apr 2007 19:49:02 +0100 [thread overview]
Message-ID: <20070409184902.GA30444@infradead.org> (raw)
In-Reply-To: <46156F60.1040400@redhat.com>
On Thu, Apr 05, 2007 at 05:51:28PM -0400, Wendy Cheng wrote:
> By writing exported filesytem id into /proc/fs/nfsd/nlm_unlock, this
> patch walks thru lockd's global nlm_files list to release all the locks
> associated with the particular id. It is used to enable NFS lock
> failover with active-active clustered servers.
>
> Relevant steps:
> 1) Exports filesystem with "fsid" option as:
> /etc/exports entry> /mnt/shared/exports *(fsid=1234,sync,rw)
> 2) Drops locks based on fsid by:
> shell> echo 1234 > /proc/fs/nfsd/nlm_unlock
This is a very awkward API. Dropping locks should support uuid or
dev_t based exports aswell. Also it would be nice if you we had
a more general push api for changes to filesystem state, that works
on a similar basis as getting information from /etc/exports.
And please inline your patches into the mail I send, attaching them
makes it really hard to quote it in mail replies or even to simply read
it.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Wendy Cheng <wcheng@redhat.com>
Cc: cluster-devel@redhat.com, Lon Hohberger <lhh@redhat.com>,
nfs@lists.sourceforge.net
Subject: Re: [PATCH 1/4 Revised] NLM - drop per fsid locks
Date: Mon, 9 Apr 2007 19:49:02 +0100 [thread overview]
Message-ID: <20070409184902.GA30444@infradead.org> (raw)
In-Reply-To: <46156F60.1040400@redhat.com>
On Thu, Apr 05, 2007 at 05:51:28PM -0400, Wendy Cheng wrote:
> By writing exported filesytem id into /proc/fs/nfsd/nlm_unlock, this
> patch walks thru lockd's global nlm_files list to release all the locks
> associated with the particular id. It is used to enable NFS lock
> failover with active-active clustered servers.
>
> Relevant steps:
> 1) Exports filesystem with "fsid" option as:
> /etc/exports entry> /mnt/shared/exports *(fsid=1234,sync,rw)
> 2) Drops locks based on fsid by:
> shell> echo 1234 > /proc/fs/nfsd/nlm_unlock
This is a very awkward API. Dropping locks should support uuid or
dev_t based exports aswell. Also it would be nice if you we had
a more general push api for changes to filesystem state, that works
on a similar basis as getting information from /etc/exports.
And please inline your patches into the mail I send, attaching them
makes it really hard to quote it in mail replies or even to simply read
it.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-09 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 21:51 [Cluster-devel] [PATCH 1/4 Revised] NLM - drop per fsid locks Wendy Cheng
2007-04-05 21:51 ` Wendy Cheng
2007-04-09 18:49 ` Christoph Hellwig [this message]
2007-04-09 18:49 ` Christoph Hellwig
2007-04-09 22:56 ` [Cluster-devel] Re: [NFS] " S. Wendy Cheng
2007-04-09 22:56 ` S. Wendy Cheng
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=20070409184902.GA30444@infradead.org \
--to=hch@infradead.org \
/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.