From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: "Adamson, Andy" <William.Adamson@netapp.com>,
Martin Houry <martinhoury@gmail.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking"
Date: Wed, 17 Feb 2016 15:59:29 -0500 [thread overview]
Message-ID: <20160217205929.GF10401@fieldses.org> (raw)
In-Reply-To: <B10307D6-13C6-4A04-B3A9-B66C27F51E19@oracle.com>
On Wed, Feb 17, 2016 at 02:06:35PM -0500, Chuck Lever wrote:
>
> > On Feb 17, 2016, at 9:50 AM, Adamson, Andy
> > <William.Adamson@netapp.com> wrote: Thanks for testing. As Trond
> > pointed out, the correct way to indicate multiple hostnames is on
> > the mount command line
> >
> > mount -o minorversion=1 host1,host2,…,hostn:/<export> /<mntdir>
>
> It might be more natural for NFSv4.x to use a referral or a pNFS
> layout instead. Do you think that's a viable approach?
Seems like an easy application for fs_locations{_info?}. It'd need
server support too, and I think you probably want this manual method as
well for now.
I wonder if the server can easily generate a list of IP addresses to
advertise automatically? In which case the whole thing would be
zero-configuration, which would be nice.
pNFS sounds like overkill.
--b.
next prev parent reply other threads:[~2016-02-17 20:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 10:31 "Re: [PATCH RFC Version 1 0/6] Request for Comment: NFS4.1 Session Trunking" Martin Houry
2016-02-17 14:50 ` Adamson, Andy
2016-02-17 16:34 ` J. Bruce Fields
2016-02-17 17:49 ` Adamson, Andy
2016-02-17 18:44 ` J. Bruce Fields
2016-02-17 19:57 ` Adamson, Andy
2016-02-17 19:06 ` Chuck Lever
2016-02-17 20:59 ` J. Bruce Fields [this message]
2016-02-17 22:35 ` Adamson, Andy
2016-02-17 22:52 ` Chuck Lever
2016-02-17 23:55 ` Trond Myklebust
2016-02-18 14:14 ` J. Bruce Fields
2016-02-18 14:38 ` Martin Houry
2016-02-18 18:32 ` Trond Myklebust
2016-02-18 19:41 ` Adamson, Andy
2016-02-18 20:39 ` J. Bruce Fields
2016-02-18 21:29 ` Chuck Lever
2016-02-19 15:01 ` J. Bruce Fields
2016-02-19 16:29 ` Chuck Lever
2016-02-18 14:05 ` J. Bruce Fields
2016-02-18 11:28 ` Martin Houry
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=20160217205929.GF10401@fieldses.org \
--to=bfields@fieldses.org \
--cc=William.Adamson@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=martinhoury@gmail.com \
--cc=trond.myklebust@primarydata.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