From: Stijn De Weirdt <stijn.deweirdt@ugent.be>
To: linux-nfs@vger.kernel.org
Subject: replicas and client support
Date: Mon, 15 Apr 2013 17:43:32 +0200 [thread overview]
Message-ID: <516C2024.9030504@ugent.be> (raw)
hi all,
(pls keep me in cc, i'm not subscribed to this list)
i am trying out the replicas feature of exportfs, but i'm unable to get
it working.
i would like to know if what i'm trying to is actually implemented in
linux (or intended behaviour of replicas in the first place).
2 nfs4 servers with cluster filesystem (gpfs in my case). the os is
sl6.4, i've enabled the nfs version 4.1 on the server (from my
understanding, 4.0 should be enough?).
i would like to test if the replicas features can be used for failover
support of a rw nfs export. ie
a. mount nfs from server1 on client
b. start some IO activity on client on the mounted filesystem
c. poweroff server1
d. after a certain amount of time, IO continues using server2
(the client i'm testing with is also el6.4 atm.)
many thanks,
stijn
next reply other threads:[~2013-04-15 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 15:43 Stijn De Weirdt [this message]
2013-04-18 19:23 ` replicas and client support J. Bruce Fields
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=516C2024.9030504@ugent.be \
--to=stijn.deweirdt@ugent.be \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox