From: "Brian J. Murrell" <brian-SquOHqY54CVWr29BmMi2cA@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Re: stuck/hung nfsv4 mounts
Date: Mon, 03 Nov 2008 15:09:18 -0500 [thread overview]
Message-ID: <1225742958.2247.128.camel@brian-laptop> (raw)
In-Reply-To: <4d569c330811031158r26963e0w5bcf8331e0fb14b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 2008-11-03 at 14:58 -0500, Kevin Coffman wrote:
>
> These are all from librpcsecgss (from the -rrr). I don't see an error here.
Good.
> You should have gotten output from gssd itself as well. You might
> also look for any errors on the server from rpc.svcgssd.
Nothing.
> This looks fine. (Assuming linux.interlinx.bc.ca is the NFS server
> and pc.interlinx.bc.ca is the client.)
Indeed, they both are as you assume.
So I've restarted both the rpc.svcgssd and rpc.gssd with -rrr -vvv on
the server and client (respectively) to see what more I can see but I
can't get the upcall to trigger. I would have thought simply issuing a
mount would do that, but it seems not. What exactly causes the upcall
to be made and what might prevent it from being made?
b.
next prev parent reply other threads:[~2008-11-03 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 15:05 stuck/hung nfsv4 mounts Brian J. Murrell
2008-11-03 16:59 ` Trond Myklebust
[not found] ` <1225731544.6958.6.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-03 17:25 ` Jim Rees
2008-11-03 17:37 ` Trond Myklebust
[not found] ` <1225733834.6958.12.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-11-03 21:40 ` Chuck Lever
2008-11-03 22:20 ` Peter Staubach
2008-11-03 22:47 ` Chuck Lever
2008-11-04 16:03 ` Peter Staubach
2008-11-03 17:38 ` Benny Halevy
2008-11-03 17:50 ` Brian J. Murrell
2008-11-03 19:58 ` Kevin Coffman
[not found] ` <4d569c330811031158r26963e0w5bcf8331e0fb14b7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 20:09 ` Brian J. Murrell [this message]
2008-11-03 20:28 ` Kevin Coffman
[not found] ` <4d569c330811031228r5bb9aefs7a970303910810e2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 21:12 ` Brian J. Murrell
2008-11-03 22:33 ` Kevin Coffman
[not found] ` <4d569c330811031433k7ae18d4enfbda349e8f90a951-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-11-03 23:45 ` Brian J. Murrell
2008-11-04 1:24 ` Brian J. Murrell
2008-11-04 15:14 ` Brian J. Murrell
2008-11-04 17:22 ` Kevin Coffman
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=1225742958.2247.128.camel@brian-laptop \
--to=brian-squohqy54cvwr29bmmi2ca@public.gmane.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.