From: Dave Reisner <d@falconindy.com>
To: linux-nfs@vger.kernel.org
Subject: First NFS mount is delayed in 3.10
Date: Sun, 28 Jul 2013 16:14:57 -0400 [thread overview]
Message-ID: <20130728201457.GA674@rampage> (raw)
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
next reply other threads:[~2013-07-28 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 20:14 Dave Reisner [this message]
2013-07-28 20:55 ` First NFS mount is delayed in 3.10 Chuck Lever
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=20130728201457.GA674@rampage \
--to=d@falconindy.com \
--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