From: "J. Bruce Fields" <bfields@fieldses.org>
To: Maiko Langelaar <maiko@physics.umanitoba.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: 2 NFS server for the same mount point ?
Date: Tue, 24 Jul 2012 13:26:16 -0400 [thread overview]
Message-ID: <20120724172616.GJ8570@fieldses.org> (raw)
In-Reply-To: <500ED5E4.1050902@physics.umanitoba.ca>
On Tue, Jul 24, 2012 at 12:05:40PM -0500, Maiko Langelaar wrote:
> > Yes, you can.
>
> Just to be on the safe side, I should be a bit more clear on this.
>
> Both of the NFS servers will be running simultaneously, both
> exporting the same mount points for the same subnet.
If you're asking whether it's safe for A and B to both be exporting
something named (for example) "/home"--sure, that's fine.
(If you want the exports from both servers to actually see the same
data, with changes made through A reflected on B and vice versa--at that
point you need a cluster filesystem backing the exports and things
become more complicated. But I think that's not what you're asking
for.)
--b.
prev parent reply other threads:[~2012-07-24 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:12 2 NFS server for the same mount point ? Maiko Langelaar
2012-07-24 15:53 ` Malahal Naineni
2012-07-24 17:05 ` Maiko Langelaar
2012-07-24 17:26 ` J. Bruce Fields [this message]
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=20120724172616.GJ8570@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=maiko@physics.umanitoba.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.