From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jim Schutt <jaschut@sandia.gov>,
"Adamson, Dros" <Weston.Adamson@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 20:40:58 +0000 [thread overview]
Message-ID: <1369946457.3111.17.camel@leira.trondhjem.org> (raw)
In-Reply-To: <D74C8145-AD4D-4CFE-963C-643B8D7DBA10@oracle.com>
On Thu, 2013-05-30 at 16:26 -0400, Chuck Lever wrote:
> 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?
>
For some reason it got lost in the mail heap. I've applied it now to the
'bugfixes' branch. Will push upstream in the next few days...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2013-05-30 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 20:19 Jim Schutt
2013-05-30 20:26 ` Chuck Lever
2013-05-30 20:40 ` Myklebust, Trond [this message]
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=1369946457.3111.17.camel@leira.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=Weston.Adamson@netapp.com \
--cc=chuck.lever@oracle.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
all inboxes | Powered by JetHome®