Failure to mount nfsv4 on 3.12.0-rc5-wl+
Subsystems (2)
This is on an un-hacked upstream kernel (ath tree). Mounting an older Fedora 13 system with nfsv3 works fine, but mounting a F17 box with NFSv4 hangs. Ctrl-c of the process yields this error:
NFS: nfs4_discover_server_trunking unhandled error -512. Exiting with error EIO
3.9 kernels on this same system mount the F17 box fine.
If I add 'vers=3' to /etc/fstab, then it mounts the F17 box fine.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 5 lines · Ben Greear
This is on an un-hacked upstream kernel (ath tree). Mounting an older Fedora 13 system with nfsv3 works fine, but mounting a F17 box with NFSv4 hangs. Ctrl-c of the process yields this error:
NFS:
nfs4_discover_server_trunkingunhandled error -512. Exiting with error EIO
I have seen this error message and I'm currently debugging it - it's due to a hang in GSSD upcall. This message is generated when the user ^Cs the mount. This is reproducible, but the hang only happens for me every once in a while. I can make it happen pretty reliably if I call mount/unmount a bunch of times (like the test_sec_options.sh script I posted last week).
This issue is next on my list...
-dros
Quoted 16 lines
3.9 kernels on this same system mount the F17 box fine.
If I add 'vers=3' to
/etc/fstab, then it mounts the F17 box fine.Thanks,
BenSignature · 7 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
… and I think it makes sense to me that this behavior was recently introduced and vers=3 fixes things, because nfsv4 has to do the upcall to GSSD even when sec=sys because it attempts to do krb5i on non superblock related operations (if possible will use, otherwise just uses sys) and this behavior was recently added. NFSv3 does not do this.
-dros
Quoted 32 lines · Weston Andros Adamson
Quoted 5 lines · Ben Greear
This is on an un-hacked upstream kernel (ath tree). Mounting an older Fedora 13 system with nfsv3 works fine, but mounting a F17 box with NFSv4 hangs. Ctrl-c of the process yields this error:
NFS:
nfs4_discover_server_trunkingunhandled error -512. Exiting with error EIOI have seen this error message and I'm currently debugging it - it's due to a hang in GSSD upcall. This message is generated when the user ^Cs the mount. This is reproducible, but the hang only happens for me every once in a while. I can make it happen pretty reliably if I call mount/unmount a bunch of times (like the
test_sec_options.shscript I posted last week).This issue is next on my list...
-dros
Quoted 16 lines
3.9 kernels on this same system mount the F17 box fine.
If I add 'vers=3' to
/etc/fstab, then it mounts the F17 box fine.Thanks,
BenSignature · 7 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Weston Andros Adamson
… and I think it makes sense to me that this behavior was recently introduced and vers=3 fixes things, because nfsv4 has to do the upcall to GSSD even when sec=sys because it attempts to do krb5i on non superblock related operations (if possible will use, otherwise just uses sys) and this behavior was recently added. NFSv3 does not do this.
-dros
I have a gssd running on the client, from what I can tell, but no idea if it is working properly or not. It should be whatever is standard with F17.
[root@ct523-9292 ~]# ps -auxww|grep gss
root 723 0.0 0.0 35192 504 ? Ss 10:17 0:00 /usr/sbin/rpc.gssd root 5975 0.0 0.0 109408 872 pts/0 S+ 10:25 0:00 grep --color=auto gss
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 7 lines · Ben Greear
Quoted 3 lines · Weston Andros Adamson
… and I think it makes sense to me that this behavior was recently introduced and vers=3 fixes things, because nfsv4 has to do the upcall to GSSD even when sec=sys because it attempts to do krb5i on non superblock related operations (if possible will use, otherwise just uses sys) and this behavior was recently added. NFSv3 does not do this.
-dros
I have a gssd running on the client, from what I can tell, but no idea if it is working properly or not. It should be whatever is standard with F17.
It's my belief that a GSSD bug is causing this hang and that the bug has been in GSSD for a while, but wasn't hit until recent kernel changes.
I'll share more as soon as I figure it out!
-dros
Quoted 12 lines
[root@ct523-9292 ~]# ps -auxww|grep gss
root 723 0.0 0.0 35192 504 ? Ss 10:17 0:00 /usr/sbin/rpc.gssd root 5975 0.0 0.0 109408 872 pts/0 S+ 10:25 0:00 grep --color=auto gssThanks,
BenSignature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com
Quoted 7 lines · Weston Andros Adamson
Quoted 4 lines · Ben Greear
This is on an un-hacked upstream kernel (ath tree). Mounting an older Fedora 13 system with nfsv3 works fine, but mounting a F17 box with NFSv4 hangs. Ctrl-c of the process yields this error:
Quoted 5 lines
Quoted 1 line
NFS:
nfs4_discover_server_trunkingunhandled error -512. Exiting with error EIOI have seen this error message and I'm currently debugging it - it's due to a hang in GSSD upcall. This message is generated when the user ^Cs the mount. This is reproducible, but the hang only happens for me every once in a while. I can make it happen pretty reliably if I call mount/unmount a bunch of times (like the
test_sec_options.shscript I posted last week).This issue is next on my list...
Ok, no problem. The vers=3 thing is fine for me.
I do seem to have a good system for reproducing the problem if you create some patches for testing...
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com