From: Shehjar Tikoo <shehjart@gluster.com>
To: <linux-nfs@vger.kernel.org>
Subject: Expected response from server not supporting v4
Date: Tue, 16 Aug 2011 13:31:38 +0530 [thread overview]
Message-ID: <4E4A23E2.3020103@gluster.com> (raw)
Hi All
The following thread discusses the behaviour when the client does not
support v4:
http://thread.gmane.org/gmane.linux.nfs/36928/
OTOH, when the server does not support v4, for eg. Gluster NFS server,
where we support only v3, I believe v4 client will attempt to connect
directly to port 2049 and receive connection failure errors on TCP. Does
the current nfs client handle the situation where this results in a timeout
for mount? We're hearing a report of a timeout occurring on the RHEL6
client because the server does not have v4 support. Could someone please
shed some light on how this behaviour is handled at present? Thanks
-Shehjar
next reply other threads:[~2011-08-16 8:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 8:01 Shehjar Tikoo [this message]
2011-08-16 12:50 ` Expected response from server not supporting v4 Steve Dickson
2011-08-17 6:35 ` Shehjar Tikoo
2011-08-17 15:27 ` Chuck Lever
[not found] ` <4E4E0171.6010104@gluster.com>
2011-08-19 16:09 ` Chuck Lever
2011-08-23 9:21 ` Shehjar Tikoo
2011-08-26 15:43 ` Chuck Lever
2011-08-26 20:19 ` Chuck Lever
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=4E4A23E2.3020103@gluster.com \
--to=shehjart@gluster.com \
--cc=linux-nfs@vger.kernel.org \
/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