Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: long delay when mounting due to SETCLIENTID AUTH_GSS attempts
Date: Tue, 7 May 2013 17:44:21 -0400	[thread overview]
Message-ID: <20130507214421.GJ32743@fieldses.org> (raw)
In-Reply-To: <1367962608.3580.10.camel@leira.trondhjem.org>

On Tue, May 07, 2013 at 09:36:49PM +0000, Myklebust, Trond wrote:
> On Tue, 2013-05-07 at 17:02 -0400, J. Bruce Fields wrote:
> > I suppose if gssd is running then it should always hold open the parent
> > (rpc_pipefs/nfs) directory.  So if that isn't open it might be safe to
> > assume we can fail immediately.
> 
> If rpc.idmapd is running, then it will do the same.

Whoops, you're right.

> One possible solution might simply be to put up a 'gssd' pipe in
> rpc_pipefs/nfs and use that as a metric. The problem is that IIRC,
> rpc.gssd will release all pipes and then reopen them on getting a new
> directory notification...

Yeah, longer term it'd be nice to have some better way to recognize when
gssd is up than that wait_for_pipe_open hack, but I don't see anything
that works with current gssd.

--b.

  reply	other threads:[~2013-05-07 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 17:25 long delay when mounting due to SETCLIENTID AUTH_GSS attempts Jeff Layton
2013-05-03 17:56 ` Chuck Lever
2013-05-03 18:24   ` Jeff Layton
2013-05-03 18:33     ` Myklebust, Trond
2013-05-03 18:44       ` Jeff Layton
2013-05-03 18:48         ` Chuck Lever
2013-05-03 19:17           ` Jeff Layton
2013-05-03 19:26             ` Chuck Lever
2013-05-03 19:39               ` Jeff Layton
2013-05-05 22:49                 ` Chuck Lever
2013-05-03 21:18           ` J. Bruce Fields
2013-05-03 21:50             ` Chuck Lever
2013-05-06 22:33               ` Chuck Lever
2013-05-07 21:02                 ` J. Bruce Fields
2013-05-07 21:21                   ` Chuck Lever
2013-05-07 21:26                     ` J. Bruce Fields
2013-05-07 21:36                   ` Myklebust, Trond
2013-05-07 21:44                     ` J. Bruce Fields [this message]
2013-05-07 20:53               ` J. Bruce Fields
2013-05-07 21:00                 ` Jeff Layton
2013-05-07 21:27                 ` 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=20130507214421.GJ32743@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.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