On Oct 22, 2013, at 1:09 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > 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 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 > > 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 > > -- > Ben Greear <greearb@xxxxxxxxxxxxxxx> > 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 majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
