linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Daniel.Muntz@emc.com
Cc: matt@linuxbox.com, rees@umich.edu, androsadamson@gmail.com,
	linux-nfs@vger.kernel.org, bhalevy@panasas.com
Subject: RE: 4.1 no-pnfs mount option?
Date: Tue, 18 Jan 2011 20:44:45 -0500	[thread overview]
Message-ID: <1295401485.2941.1.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <DE966DA98A4ABE438D726BDF1699CF61043985B639@MX05A.corp.emc.com>

On Tue, 2011-01-18 at 19:53 -0500, Daniel.Muntz@emc.com wrote: 
> 
> > -----Original Message-----
> > From: Trond Myklebust [mailto:Trond.Myklebust@netapp.com] 
> > Sent: Tuesday, January 18, 2011 11:15 AM
> > To: Matt W. Benjamin
> > Cc: Muntz, Daniel; rees@umich.edu; androsadamson@gmail.com; 
> > linux-nfs@vger.kernel.org; Benny Halevy
> > Subject: Re: 4.1 no-pnfs mount option?
> > 
> > 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?
> 
> By the same logic, why should a user be allowed to select which version of NFS they use for mounting when the server has a perfectly reasonable way of negotiating it?  Getting to choose v2 vs. v3 vs. v4 seems like much less of a distinction than choosing between pNFS and no pNFS.  Frankly, it never even occurred to me that there wouldn't be a mount option to make this choice.  Enabling/disabling the layout driver doesn't fit the existing model of choosing mount behavior, and is a big hammer--it's all or nothing.
> 
> Anyway, here's a use case: I'm working at an HPC/gas+oil/satellite data site.  We have an awesome pNFS server for our big data and I want to access my big data with pNFS.  We have another server for homedirs, some big data, and other stuff.  Some mounts are fine with pNFS, others are abysmal.  So, I want to mount some directories with pNFS, and some without pNFS, on the same client, independent of the server configuration.

mount -t nfs -overs=4,minorversion=0 foo:/ /bar

Done... Any more questions?

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com


  reply	other threads:[~2011-01-19  1:45 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
2011-01-19  0:53                   ` Daniel.Muntz
2011-01-19  1:44                     ` Trond Myklebust [this message]
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=1295401485.2941.1.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).