From: Maiko Langelaar <maiko@physics.umanitoba.ca>
To: linux-nfs@vger.kernel.org
Subject: 2 NFS server for the same mount point ?
Date: Tue, 24 Jul 2012 10:12:41 -0500 [thread overview]
Message-ID: <500EBB69.5000205@physics.umanitoba.ca> (raw)
A bit of history first.
Our original NFS server (Server A) is getting old. It exports a
bunch of files systems, ie: /home/u3, /home/u7, under which are
a bunch of user directories.
To minimize downtown, my strategy was to tackle migration to a
new NFS server (Server B) user by user (we don't have tons). In
the end what I have now is all the user directories on Server B,
but I have kept the original mount points still exported on the
Server A, with all the user subdirectories now defined as symbolic
links to the new mount points on Server B. This has worked very
well actually, very little downtime for anyone, and people did
not have to stop computation runs (some of which take weeks).
Now comes the interesting part.
I want to move the original mount points over to Server B !
Question : Can I export the SAME mount points on 2 NFS servers
for the same subnet ? I figure yes, because any particular NFS
client will *target* a particular server. BUT the RPC nature of
the NFS protocol makes me a bit nervous about doing so.
Can anyone provide their experience in this ?
For what it's worth, Server B defaults V4, Server A is V3,
with a mix of V3 and V4 clients.
Much appreciated.
Maiko Langelaar
IT Physics and Astronomy
University of Manitoba
204-474-9273
next reply other threads:[~2012-07-24 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:12 Maiko Langelaar [this message]
2012-07-24 15:53 ` 2 NFS server for the same mount point ? Malahal Naineni
2012-07-24 17:05 ` Maiko Langelaar
2012-07-24 17:26 ` 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=500EBB69.5000205@physics.umanitoba.ca \
--to=maiko@physics.umanitoba.ca \
--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;
as well as URLs for NNTP newsgroup(s).