From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/3] NLM lock failover
Date: Mon, 31 Jul 2006 21:55:41 -0400 [thread overview]
Message-ID: <1154397341.3378.10.camel@localhost.localdomain> (raw)
In-Reply-To: <44A41246.2070106@redhat.com>
For background info, please check out:
o http://www.redhat.com/archives/linux-cluster/2006-June/msg00050.html
for interface discussion.
o https://www.redhat.com/archives/cluster-devel/2006-June/msg00231.html
for first drafted code review.
Note and Restrictions:
o With nfs-utils-1.0.8-rc4 and nfs-utils-lib-1.0.8, the tests went
surprisingly well, particularly the ha-callout feature. *No* change
is made into these two user mode utility packages.
o The nfs-utils config flag RESTRICTED_STATD must be off for NLM
failover to be functional correctly.
o The third parameter passed to rpc.statd ha-callout program is no
longer be the system_utsname.nodename (set by sethostname()). It
is, instead, the specific IP interface where the server receives
the client's request.
o The patches are for NFS v2/v3 only. However, we do leave room for
future NFS V4 expansion. For example, echoing client_ip at server_ip
into /proc/fs/nfsd/nlm_unlock could be used to drop the V4 locks.
o IP V6 modification is not included in this patch set. If required,
it will be submitted as another patch set.
PATCH 1/3
---------
Add a new admin interface into current nfsd procfs filesystem to trigger
NLM lock releasing logic. The command is invoked by echoing the server
IP V4 address (in standard dot notation) into /proc/fs/nfsd/nlm_unlock
file as:
shell> cd /prod/fs/nfsd
shell> echo 10.10.1.1 > nlm_unlock
PATCH 2/3
---------
Add take-over server counter-part command into nfsd procfs interface to
allow selectively setting of per (virtual) ip (lockd) grace period. The
grace period setting follows current system-wide grace period rule and
default. It is also invoked by echoing the server IP V4 address (in dot
notation) into /proc/fs/nfsd/nlm_set_ip_grace file:
shell> cd /proc/fs/nfsd
shell> echo 10.10.1.1 > nlm_set_ip_grace
PATCH 3/3
---------
This kernel patch adds a new field into struct nlm_host that holds the
server IP address. Upon SM_MON and SM_UNMON procedure calls, the IP (in
standard V4 dot notation) is placed as the "my_name" string and passed
to local statd daemon. This enables ha-callout program ("man rpc.statd"
for details) to receive the IP address of the server that has received
the client's request. Before this change, my_name string is universally
set to system_utsname.nodename.
The user mode HA implementation is expected to:
1. Specify a user mode ha-calloupt program (rpc.statd -H) for receiving
client monitored states.
2. Based on info passed by ha-callout, individual state-directory should
be created and can be read from take-over server.
3. Upon failover, on take-over server, send out notification to nfs
client via (rpc.statd -n server_ip -P individual_state_directory -N)
command.
-- Wendy
WARNING: multiple messages have this Message-ID (diff)
From: Wendy Cheng <wcheng@redhat.com>
To: nfs@lists.sourceforge.net
Cc: cluster-devel@redhat.com, lhh@redhat.com
Subject: [PATCH 0/3] NLM lock failover
Date: Mon, 31 Jul 2006 21:55:41 -0400 [thread overview]
Message-ID: <1154397341.3378.10.camel@localhost.localdomain> (raw)
In-Reply-To: <44A41246.2070106@redhat.com>
For background info, please check out:
o http://www.redhat.com/archives/linux-cluster/2006-June/msg00050.html
for interface discussion.
o https://www.redhat.com/archives/cluster-devel/2006-June/msg00231.html
for first drafted code review.
Note and Restrictions:
o With nfs-utils-1.0.8-rc4 and nfs-utils-lib-1.0.8, the tests went
surprisingly well, particularly the ha-callout feature. *No* change
is made into these two user mode utility packages.
o The nfs-utils config flag RESTRICTED_STATD must be off for NLM
failover to be functional correctly.
o The third parameter passed to rpc.statd ha-callout program is no
longer be the system_utsname.nodename (set by sethostname()). It
is, instead, the specific IP interface where the server receives
the client's request.
o The patches are for NFS v2/v3 only. However, we do leave room for
future NFS V4 expansion. For example, echoing client_ip@server_ip
into /proc/fs/nfsd/nlm_unlock could be used to drop the V4 locks.
o IP V6 modification is not included in this patch set. If required,
it will be submitted as another patch set.
PATCH 1/3
---------
Add a new admin interface into current nfsd procfs filesystem to trigger
NLM lock releasing logic. The command is invoked by echoing the server
IP V4 address (in standard dot notation) into /proc/fs/nfsd/nlm_unlock
file as:
shell> cd /prod/fs/nfsd
shell> echo 10.10.1.1 > nlm_unlock
PATCH 2/3
---------
Add take-over server counter-part command into nfsd procfs interface to
allow selectively setting of per (virtual) ip (lockd) grace period. The
grace period setting follows current system-wide grace period rule and
default. It is also invoked by echoing the server IP V4 address (in dot
notation) into /proc/fs/nfsd/nlm_set_ip_grace file:
shell> cd /proc/fs/nfsd
shell> echo 10.10.1.1 > nlm_set_ip_grace
PATCH 3/3
---------
This kernel patch adds a new field into struct nlm_host that holds the
server IP address. Upon SM_MON and SM_UNMON procedure calls, the IP (in
standard V4 dot notation) is placed as the "my_name" string and passed
to local statd daemon. This enables ha-callout program ("man rpc.statd"
for details) to receive the IP address of the server that has received
the client's request. Before this change, my_name string is universally
set to system_utsname.nodename.
The user mode HA implementation is expected to:
1. Specify a user mode ha-calloupt program (rpc.statd -H) for receiving
client monitored states.
2. Based on info passed by ha-callout, individual state-directory should
be created and can be read from take-over server.
3. Upon failover, on take-over server, send out notification to nfs
client via (rpc.statd -n server_ip -P individual_state_directory -N)
command.
-- Wendy
-------------------------------------------------------------------------
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:[~2006-08-01 1:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:47 [Cluster-devel] [RFC PATCH 0/3] NLM lock failover Wendy Cheng
2006-06-29 17:47 ` Wendy Cheng
2006-08-01 1:55 ` Wendy Cheng [this message]
2006-08-01 1:55 ` [PATCH " Wendy Cheng
[not found] ` <message from Wendy Cheng on Monday July 31>
2006-08-03 4:14 ` [Cluster-devel] Re: [NFS] " Neil Brown
2006-08-03 4:14 ` Neil Brown
2006-08-03 21:34 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-07 22:38 ` Wendy Cheng
2006-08-04 9:27 ` Greg Banks
2006-08-04 9:27 ` Greg Banks
2006-08-04 13:27 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-04 13:27 ` Wendy Cheng
2006-08-04 14:56 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-04 14:56 ` Wendy Cheng
2006-08-04 15:51 ` [Cluster-devel] Re: [NFS] " Trond Myklebust
2006-08-04 15:51 ` Trond Myklebust
2006-08-05 5:44 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-05 5:44 ` Wendy Cheng
2006-08-07 4:05 ` [Cluster-devel] Re: [NFS] " Greg Banks
2006-08-07 4:05 ` Greg Banks
2006-08-07 20:14 ` [Cluster-devel] Re: [NFS] " James Yarbrough
2006-08-07 20:14 ` James Yarbrough
2006-08-07 21:03 ` [Cluster-devel] Re: [NFS] " Wendy Cheng
2006-08-07 4:05 ` Greg Banks
2006-08-07 4:05 ` Greg Banks
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=1154397341.3378.10.camel@localhost.localdomain \
--to=wcheng@redhat.com \
/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.