From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Daniel Muntz <Daniel.Muntz@emc.com>,
rees@umich.edu, androsadamson@gmail.com,
linux-nfs@vger.kernel.org, Benny Halevy <bhalevy@panasas.com>
Subject: Re: 4.1 no-pnfs mount option?
Date: Tue, 18 Jan 2011 14:35:50 -0500 (EST) [thread overview]
Message-ID: <559269113.92.1295379350636.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <553185711.90.1295379290216.JavaMail.root@thunderbeast.private.linuxbox.com>
Hi,
----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:
> "Why would an administrator never want to do this?" is not a helpful
> question.
>
> A more useful question is "what reason would you possibly have for
> overriding the server's request that you do pNFS when your client has
> pNFS support?" What makes pNFS so special that we must allow
> administrators to do this on a per-mount basis?
Well, I phrased my question the other way because I suspect such cases will be found, but I may not have found all of them.
Some thoughts on why I might wish to take a hand in the decision:
1. the client doing pnfs might behave badly due to a misconfiguration or outage, yet behave acceptably using ordinary nfsv4?
2. restricting the client to ordinary nfsv4 might be desirable for non-developer troubleshooting or other configuration work?
I apologize if neither is compelling.
>
> Throwing more and more knobs into the kernel is easy. The difficult
> bit
> is to figure out which are useful knobs, and that is why I want real
> use
> cases...
>
> Trond
>
Matt
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next parent reply other threads:[~2011-01-18 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <553185711.90.1295379290216.JavaMail.root@thunderbeast.private.linuxbox.com>
2011-01-18 19:35 ` Matt W. Benjamin [this message]
2011-01-18 19:45 ` 4.1 no-pnfs mount option? Trond Myklebust
2011-01-14 15:19 Jim Rees
2011-01-14 15:31 ` William A. (Andy) Adamson
2011-01-14 15:38 ` Jim Rees
2011-01-14 15:41 ` Trond Myklebust
2011-01-18 17:44 ` Daniel.Muntz
2011-01-18 18:28 ` Trond Myklebust
2011-01-18 18:35 ` Benny Halevy
2011-01-18 18:38 ` Trond Myklebust
2011-01-18 18:46 ` Matt W. Benjamin
2011-01-18 19:14 ` Trond Myklebust
2011-01-19 0:53 ` Daniel.Muntz
2011-01-19 1:44 ` Trond Myklebust
2011-01-19 2:29 ` Daniel.Muntz
2011-01-19 2:56 ` Trond Myklebust
2011-01-19 3:30 ` Matt W. Benjamin
2011-01-19 3:57 ` Trond Myklebust
2011-01-19 5:54 ` Daniel.Muntz
2011-01-19 14:05 ` Trond Myklebust
2011-01-19 14:27 ` Jim Rees
2011-01-18 20:25 ` Benny Halevy
2011-01-14 15:51 ` Andy Adamson
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=559269113.92.1295379350636.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=Daniel.Muntz@emc.com \
--cc=Trond.Myklebust@netapp.com \
--cc=androsadamson@gmail.com \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.