Hi, I use an extremely simple NFSv4 setup to share files between my desktop and some KVM guests. Noteworthy, I suppose, is that I'm not passing any sec= parameter with the mount options. According to the documentation, this means I'm using sec=sys. Starting with the Linux 3.10 series, there's a 15 second delay when mounting an NFS share for the first time, followed by a pair of messages generated by the sunrpc module: [ 22.206788] RPC: AUTH_GSS upcall timed out. [ 22.206788] Please check user daemon is running. The mount does succeed after this timeout, and everything behaves as expected. Subsequent mounting is fast and this seems to be a result of Linux commit abfdbd53a4e28. Additionally, if I start rpc.gssd on a client, this delay naturally goes away as the requisite userspace daemon is responsive. I can confirm that this same behavior exists on the latest from Linus's repo; git describe'd as v3.11-rc2-355-g6c504ec. I've not made any attempts to bisect this yet. Is this expected behavior? The aforementioned commit seems to claim that there's now a "stronger dependency on rpc.gssd", but the manpage for rpc.gssd seems to indicate that it's really only used for Kerberized NFS. Am I really going to need to use rpc.gssd on my clients now, even though it'll effectively be doing nothing? Any help is greatly appreciated. Please CC me on replies as I'm not subscribed to the list. Thanks, Dave -- 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
