From: Wendy Cheng <wcheng@redhat.com>
To: nfs@lists.sourceforge.net, cluster-devel@redhat.com
Cc: Lon Hohberger <lhh@redhat.com>
Subject: [RFC PATCH 0/3] NLM lock failover
Date: Thu, 29 Jun 2006 13:47:50 -0400 [thread overview]
Message-ID: <44A41246.2070106@redhat.com> (raw)
The uploaded patches implement NLM lock failover as discussed in:
http://www.redhat.com/archives/linux-cluster/2006-June/msg00050.html
[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
virtual IP address into /proc/fs/nfsd/nlm_unlock file as:
shell> cd /prod/fs/nfsd
shell> echo 10.10.1.1 > nlm_unlock
It is currently restricted to IPV4 addressing and the command should be
invoked from the taken-over NFS server. To do list (not yet implemented)
include:
1. IPv6 addessing enablement
2. Add "client:server" ip pair to allow NFS V4 lock failover as proposed
by Andy Adamson (CITI).
[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. It
is also invoked by echoing the virtual IP into
/proc/fs/nfsd/nlm_set_ip_grace file as:
shell> cd /proc/fs/nfsd
shell> echo 10.10.1.1 > nlm_set_ip_grace
It is also restricted to IPV4 addressing and the command is expected to
be invoked from the take-over NFS server.
[PATCH 3/3]
This kernel patch has *not* been unit tested out yet and it needs to be
paired with user mode nfs-utils changes (not ready in time for this
RFC). It puts the taken-over IPv4 address in standard dot notation into
the 3rd parameter of ha_callout program (see man rpc.statd for details)
for "add-client" event. For "del-client", we would assume the monitored
host should be removed from machine-wide lists, regardless server's
interface.
Upon agree-ed on, we will integrate the changes into our cluster suite
to start a full function verification test. Please comment.
-- Wendy
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
next reply other threads:[~2006-06-29 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 17:47 Wendy Cheng [this message]
2006-08-01 1:55 ` [PATCH 0/3] NLM lock failover Wendy Cheng
2006-08-03 4:14 ` Neil Brown
2006-08-04 9:27 ` Greg Banks
2006-08-04 13:27 ` Wendy Cheng
2006-08-04 14:56 ` Wendy Cheng
2006-08-04 15:51 ` Trond Myklebust
2006-08-05 5:44 ` Wendy Cheng
2006-08-07 4:05 ` Greg Banks
2006-08-07 20:14 ` James Yarbrough
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=44A41246.2070106@redhat.com \
--to=wcheng@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=lhh@redhat.com \
--cc=nfs@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox