From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "Matt W. Benjamin" <matt@linuxbox.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:14:35 -0500 [thread overview]
Message-ID: <1295378075.3746.37.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <2129226927.80.1295376390168.JavaMail.root@thunderbeast.private.linuxbox.com>
On Tue, 2011-01-18 at 13:46 -0500, Matt W. Benjamin wrote:
> Hi,
>
> Isn't by mount a plausible way to select for pnfs independent of debugging? Is it assured that a client administrator would never reasonably wish to do this?
"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?
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
> ----- "Trond Myklebust" <Trond.Myklebust@netapp.com> wrote:
>
> > >
> > > Such a mount option could be useful for dealing with buggy servers
> > (pnfs-wise) so you
> > > could mount one server with pnfs and another without.
> >
> > You can find ways around that. Just use 2 clients: one with pnfs
> > switched on, and one with it off.
> >
> > I really don't want to introduce mount options upstream unless they
> > are
> > useful in the long term. One off usefulness does not pass that test.
> >
> > --
> > Trond Myklebust
> > Linux NFS client maintainer
> >
> > NetApp
> > Trond.Myklebust@netapp.com
> > www.netapp.com
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs"
> > in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-01-18 19:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 15:19 4.1 no-pnfs mount option? 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 [this message]
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
[not found] <553185711.90.1295379290216.JavaMail.root@thunderbeast.private.linuxbox.com>
2011-01-18 19:35 ` Matt W. Benjamin
2011-01-18 19:45 ` Trond Myklebust
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=1295378075.3746.37.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=Daniel.Muntz@emc.com \
--cc=androsadamson@gmail.com \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=matt@linuxbox.com \
--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 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).