From: Tom Haynes <loghyr@excfb.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andy Adamson <androsadamson@gmail.com>,
Chuck Lever <chuck.lever@oracle.com>,
"Adamson, Andy" <William.Adamson@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Configuring flex file DS on Linux upstream
Date: Thu, 26 May 2016 11:31:34 -0700 [thread overview]
Message-ID: <20160526183134.GA30979@psyklo.internal.excfb.com> (raw)
In-Reply-To: <20160526152253.GC21450@fieldses.org>
fwiw, I'm looking at being able to specify a remote DS for the next version
of the flex file server. Is it worth considering that in the discussion
being done in Andy's thread about "Configuring fs_locations on Linux upstream server pseudo fs for session trunking"?
For example:
/mds *(rw,pnfs,ff_ds=192.168.2.101.2049:/ds,insecure,no_root_squash,no_all_squash)
And in the far future, I'd want it to be a multipath list.
I don't see this as something that changes often and the exports
seem like the most natural fit.
next prev parent reply other threads:[~2016-05-26 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04273F60-806B-4E12-B097-388C346F2DED@oracle.com>
2016-05-25 17:29 ` Configuring fs_locations on Linux upstream server pseudo fs for session trunking Adamson, Andy
2016-05-25 18:48 ` bfields
2016-05-25 18:55 ` Chuck Lever
2016-05-26 13:54 ` Andy Adamson
2016-05-26 14:25 ` Chuck Lever
2016-05-26 14:44 ` Adamson, Andy
2016-05-26 15:22 ` Chuck Lever
2016-06-13 17:30 ` J. Bruce Fields
2016-05-26 15:22 ` J. Bruce Fields
2016-05-26 18:31 ` Tom Haynes [this message]
2016-05-26 18:41 ` Configuring flex file DS on Linux upstream J. Bruce Fields
2016-05-26 19:33 ` Adamson, Andy
2016-05-26 20:51 ` Tom Haynes
2016-05-31 18:31 ` Configuring fs_locations on Linux upstream server pseudo fs for session trunking Steve Dickson
2016-05-31 18:23 ` Steve Dickson
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=20160526183134.GA30979@psyklo.internal.excfb.com \
--to=loghyr@excfb.com \
--cc=William.Adamson@netapp.com \
--cc=androsadamson@gmail.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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 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.