From: Jim Rees <rees@umich.edu>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Daniel.Muntz@emc.com, matt@linuxbox.com, androsadamson@gmail.com,
linux-nfs@vger.kernel.org, bhalevy@panasas.com
Subject: Re: 4.1 no-pnfs mount option?
Date: Wed, 19 Jan 2011 09:27:52 -0500 [thread overview]
Message-ID: <20110119142752.GB6026@merit.edu> (raw)
In-Reply-To: <1295445912.3444.10.camel@heimdal.trondhjem.org>
Have we beaten this dead horse to a pulp yet? I was just asking if there
was such an option, not advocating for adding one. It would have been
useful at the time for my own testing but I can see the argument against
adding unwanted knobs.
The discussion has been useful in one way. I will now be spending some time
making sure the block layout driver falls back gracefully to no-pnfs if, for
example, an iscsi target can't be contacted.
next prev parent reply other threads:[~2011-01-19 14:27 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
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 [this message]
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=20110119142752.GB6026@merit.edu \
--to=rees@umich.edu \
--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=matt@linuxbox.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;
as well as URLs for NNTP newsgroup(s).