From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: linux-nfs@vger.kernel.org
Subject: NFSv4 high availability setups
Date: Thu, 5 Apr 2012 12:31:24 +0200 [thread overview]
Message-ID: <20120405103124.GV4752@ics.muni.cz> (raw)
Hi,
we got several front-ends for a shared storage. We want to build HA setup so
that failed front-end fails over to another front-end (that is serving NFSv4
already).
As I understand, NFS4 uses state dir somewhere in /var/lib/nfs/rpc_pipefs.
Can we put this state dir on a shared volume so that this state dir is common
for all the front-ends serving the same content? Is is supposed to work and
NFSv4 can merge its state with existing state on a shared disk?
--
Lukáš Hejtmánek
next reply other threads:[~2012-04-05 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 10:31 Lukas Hejtmanek [this message]
2012-04-05 11:39 ` NFSv4 high availability setups Jeff Layton
2012-04-10 12:55 ` Lukas Hejtmanek
2012-04-10 13:13 ` Jeff Layton
2012-04-10 18:14 ` Michael Schwartzkopff
2012-04-17 14:34 ` Lukas Hejtmanek
2012-04-17 15:14 ` Jeff Layton
2012-04-24 14:01 ` Jeff Layton
2012-04-24 14:28 ` Chuck Lever
2012-04-24 15:19 ` Jeff Layton
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=20120405103124.GV4752@ics.muni.cz \
--to=xhejtman@ics.muni.cz \
--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