Skip to contentSkip to conversation

3.10-rc3 NFSv3 mount issues

DISCUSSION Jim Schutt 3 participants 4 messages May 30, 2013

Subsystems (2)
lore
Share & tools
lore

Jim Schutt

author
#0 lore raw

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?

Thanks -- Jim

#1 lore raw
Quoted 26 lines · Jim Schutt

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'

Quoted 7 lines

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?

Signature · 2 lines
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
#2 lore raw
Quoted 36 lines · Chuck Lever
Quoted 26 lines · Jim Schutt

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'

Quoted 7 lines

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?

Quoted 6 lines

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...

Signature · 6 lines
Trond Myklebust
Linux NFS client maintainer

NetApp
[email protected]
www.netapp.com