From: Chuck Lever <chuck.lever@oracle.com>
To: Jim Schutt <jaschut@sandia.gov>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Weston Andros Adamson <dros@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.10-rc3 NFSv3 mount issues
Date: Thu, 30 May 2013 16:26:12 -0400 [thread overview]
Message-ID: <D74C8145-AD4D-4CFE-963C-643B8D7DBA10@oracle.com> (raw)
In-Reply-To: <51A7B442.9010108@sandia.gov>
On May 30, 2013, at 4:19 PM, Jim Schutt <jaschut@sandia.gov> wrote:
> Hi,
>
> I've been trying to test 3.10-rc3 on some diskless clients, and found
> that I can no longer mount my root file system via NFSv3.
>
> I poked around looking at NFS changes for 3.10, and found these two
> commits:
>
> d497ab9751 "NFSv3: match sec= flavor against server list"
> 4580a92d44 "NFS: Use server-recommended security flavor by default (NFSv3)"
>
> If I revert both of these commits from 3.10-rc3, then my diskless
> client can mount its root file system.
>
> The busybox mount command fails like this, when using 3.10-rc3:
>
> / # mount -t nfs -o ro,nolock,vers=3,proto=tcp 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x /mnt
> mount: mounting 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x on /mnt failed: Invalid argument
>
> The commit messages for both these commits seem to say that mounting
> with the "sys=sec" option should work, but unfortunately, my busybox doesn't
> seem to understand the "sec=" mount option:
>
> / # mount -t nfs -o ro,nolock,vers=3,proto=tcp,sec=sys 172.17.0.122:/gmi/images/jaschut/ceph.toss-2x /mnt
> mount: invalid number 'sys'
>
> My NFS server is based on RHEL6, and is not using any "sec=" option
> in its export for this file system. I did try exporting with "sec=sys",
> but it didn't seem to make any difference either.
>
> So far, this seems like a regression to me ....
> Any ideas what I might be doing wrong? How can I
> help make this work again?
3.10-rc3 appears to be missing the fix for this. See:
http://marc.info/?l=linux-nfs&m=136855668104598&w=2
Trond, can we get this applied?
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2013-05-30 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 20:19 3.10-rc3 NFSv3 mount issues Jim Schutt
2013-05-30 20:26 ` Chuck Lever [this message]
2013-05-30 20:40 ` Myklebust, Trond
2013-05-30 20:51 ` Jim Schutt
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=D74C8145-AD4D-4CFE-963C-643B8D7DBA10@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Trond.Myklebust@netapp.com \
--cc=dros@netapp.com \
--cc=jaschut@sandia.gov \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).