From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [NFS] [PATCH 0/3] NLM lock failover
Date: Mon, 07 Aug 2006 17:03:11 -0400 [thread overview]
Message-ID: <44D7AA8F.4020109@redhat.com> (raw)
In-Reply-To: <44D79F26.B93E5C00@sgi.com>
James Yarbrough wrote:
>>>take-over server:
>>>B-1. mount the subject filesystem
>>>B-2. "echo 1234 > /proc/fs/nfsd/nlm_set_ip_grace"
>>>B-3. "rpc.statd -n 10.10.1.1 -N -P /shared_storage/sm_10.10.1.1"
>>>B-4. bring up 10.10.1.1
>>>B-5. re-export the filesystem
>>>
>>>
>>Umm, don't you want to do B-3 after B-4 and B-5 ? Otherwise
>>clients might racily fail on the first try.
>>
>>
>
>I don't think they will necessrily fail. It depends on whether the
>server sends ICMP unreachable messages and how the client responds to
>those. In any case, I think the ordering should be B-5, B-4, and B-3
>last. One can argue about the ordering of B-3 and B-4, but if exporting
>(B-5) does not happen before bringing up the IP address (B-4), clients
>can get ESTALE replies. For better transparency, it's probably best
>to avoid ESTALE.
>
>It's probably OK to do step B-3 after bringing up the IP address since
>that will mimic what happens during boot.
>
>
Yes, you and Greg are mostly right - that was an oversight from my test
script. But our user mode RHCS script (Lon wrote that piece of code)
does it correctly. He did B-5, B-4, and B-3 last.
<info> Adding export: *:/mnt/tank1 (fsid=9468,rw)
<info> Adding export: *:/mnt/tank2 (fsid=661,rw)
<debug> Link for eth0: Detected
<info> Adding IPv4 address 10.15.89.203 to eth0
<debug> Sending gratuitous ARP: 10.15.89.203 00:30:48:27:92:d6 brd
ff:ff:ff:ff:ff:ff
<info> Sending reclaim notifications via tank-02
Start of nfs1 complete
-- Wendy
next prev parent reply other threads:[~2006-08-07 21:03 UTC|newest]
Thread overview: 14+ 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-08-01 1:55 ` [Cluster-devel] [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 21:34 ` Wendy Cheng
2006-08-07 22:38 ` Wendy Cheng
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 21:03 ` Wendy Cheng [this message]
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=44D7AA8F.4020109@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).