From: Anders Blomdell <anders.blomdell@control.lth.se>
To: linux-nfs@vger.kernel.org
Subject: Mount regression between 4.0.4 client and 2.6.35 server
Date: Thu, 18 Jun 2015 10:04:29 +0200 [thread overview]
Message-ID: <55827B8D.3070103@control.lth.se> (raw)
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
I have a problem with a 4.0.4 client refusing to mount from a 2.6.35 server
due to NFS4ERR_INVAL returned during nfs4_discover_server_trunking. See
https://bugzilla.redhat.com/show_bug.cgi?id=1228272.
Proposed patch attached.
Regards
Anders Blomdell
--
Anders Blomdell Email: anders.blomdell@control.lth.se
Department of Automatic Control
Lund University Phone: +46 46 222 4625
P.O. Box 118 Fax: +46 46 138118
SE-221 00 Lund, Sweden
[-- Attachment #2: nfs4_discover_server_trunking-eio.patch --]
[-- Type: text/x-patch, Size: 866 bytes --]
Minimum viable patch to continue version autonegotiotion in
case where the server returns an unexpected NFS4ERR_INVAL,
which happens for a 4.0.4-303.fc22.x86_64 client talking to
a 2.6.35.14-106.fc14.i686.PAE server, see
https://bugzilla.redhat.com/show_bug.cgi?id=1228272
Signed-off-by: Anders Blomdell <anders.blomdell@control.lth.se>
--- utils/mount/stropts.c.orig 2015-06-18 09:51:02.091148891 +0200
+++ utils/mount/stropts.c 2015-06-18 09:48:56.859970023 +0200
@@ -838,6 +838,10 @@ check_result:
return result;
switch (errno) {
+ case EIO:
+ /* Fix to handle nfs4_discover_server_trunking returning
+ * EIO in case where nfs server returns NFS4ERR_INVAL,
+ * see https://bugzilla.redhat.com/show_bug.cgi?id=1228272 */
case EPROTONOSUPPORT:
/* A clear indication that the server or our
* client does not support NFS version 4 and minor */
next reply other threads:[~2015-06-18 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 8:04 Anders Blomdell [this message]
2015-06-18 11:49 ` Mount regression between 4.0.4 client and 2.6.35 server Trond Myklebust
2015-06-18 12:28 ` Anders Blomdell
2015-06-18 12:53 ` Trond Myklebust
2015-06-18 14:20 ` Steve Dickson
2015-06-26 12:17 ` Benjamin Coddington
2015-06-26 17:50 ` J. Bruce Fields
2015-06-26 17:58 ` Trond Myklebust
2015-06-26 18:32 ` J. Bruce Fields
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=55827B8D.3070103@control.lth.se \
--to=anders.blomdell@control.lth.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.