public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Horsley <tom.horsley@ccur.com>
To: <linux-nfs@vger.kernel.org>
Subject: Version negotiation thwarted by proto=udp mount option
Date: Wed, 8 Jan 2014 13:04:36 -0500	[thread overview]
Message-ID: <20140108130436.1e7b3157@tomh> (raw)

This is from redhat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1049032

I was asked to send mail here to see what nfs devs think about the problem.

I had the "proto=udp" option on some NFS mount lines in my fstab.
It was there because previous versions of nfs-utils apparently
ceased being able to talk to old servers at one point in time.
This option worked fine and got me connecting to the old servers.

Now a new nfs-utils came along and tries NFSv4 by default
first thing. That always rejects the mount options because
it doesn't support proto=udp at all. This leads the nfs-utils
to error out without trying a different version, so basically
my working fstab ceased to work.

I made it work again by changing to nfsvers=3 instead of
proto=udp. (But nfsvers=3 wasn't working at some point,
which was why I used proto=udp :-).

                 reply	other threads:[~2014-01-08 18:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140108130436.1e7b3157@tomh \
    --to=tom.horsley@ccur.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