From: Jim Rees <rees@umich.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Neil Brown <neilb@suse.de>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: mount.nfs: protocol fallback when server doesn't support TCP
Date: Thu, 26 Aug 2010 11:27:02 -0400 [thread overview]
Message-ID: <20100826152702.GB23940@merit.edu> (raw)
In-Reply-To: <659EE931-F48E-4A5D-9212-D4F8AE421029@oracle.com>
Chuck Lever wrote:
On Aug 25, 2010, at 10:06 PM, Neil Brown wrote:
> Maybe the ideal would be to do a portmap probe and only fall back to v3 if
> portmap confirm that v3 is supported and v4 isn't.
What are the risks of checking portmap in this case? That seems like it
would give a better chance of a desirable outcome.
In general, portmap can't confirm that v4 isn't available, only that v3 is.
Right?
next prev parent reply other threads:[~2010-08-26 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 2:06 mount.nfs: protocol fallback when server doesn't support TCP Neil Brown
2010-08-26 14:51 ` Chuck Lever
2010-08-26 15:27 ` Jim Rees [this message]
2010-08-26 16:09 ` Chuck Lever
2010-08-30 0:30 ` Neil Brown
2010-08-30 19:29 ` Chuck Lever
2010-08-31 1:00 ` Neil Brown
2010-08-31 16:38 ` Chuck Lever
2010-09-07 1:32 ` Neil Brown
2010-09-07 17:37 ` Chuck Lever
2010-09-08 2:35 ` Neil Brown
2010-09-08 18:52 ` Chuck Lever
2010-08-31 20:29 ` Chuck Lever
2010-09-07 0:02 ` Neil Brown
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=20100826152702.GB23940@merit.edu \
--to=rees@umich.edu \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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