From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Error: state manager failed on NFSv4 server linux with error 127
Date: Sat, 30 Oct 2010 13:52:31 -0400 [thread overview]
Message-ID: <1288461151.3238.9.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1288460514.32627.105.camel@pc>
On Sat, 2010-10-30 at 13:41 -0400, Brian J. Murrell wrote:
> On Sun, 2010-10-17 at 14:35 -0400, Trond Myklebust wrote:
> >
> > Error 127 is EKEYEXPIRED. It means that the RPCSEC_GSS context for at
> > least one of your threads has expired.
> >
> > Sigh... It looks as if we have a really poor handling of that in the
> > recovery threads.
> >
> > Does the following patch help?
>
> Well, while I don't seem to have had any of the state manager failed
> errors, I did have a number of processes blocked in NFS4 today with the
> patched kernel running:
>
> [316999.281908] SysRq : Show Blocked State
> [316999.285576] task PC stack pid father
> [316999.285576] rhythmbox D f32d1c9c 0 12726 12614 0x00000000
<snip>
>
> Maybe the above is an unrelated problem?
The processes appeared to be waiting for state recovery to complete, but
your trace didn't contain any evidence that a state recovery thread was
running. Did you over-edit the trace output, or was this really all?
Trond
next prev parent reply other threads:[~2010-10-30 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 17:51 Error: state manager failed on NFSv4 server linux with error 127 Brian J. Murrell
2010-10-17 18:35 ` Trond Myklebust
2010-10-30 17:41 ` Brian J. Murrell
2010-10-30 17:52 ` Trond Myklebust [this message]
2010-10-30 17:59 ` Brian J. Murrell
2010-10-30 18:19 ` Trond Myklebust
2010-10-30 19:53 ` Brian J. Murrell
2010-10-30 20:24 ` Trond Myklebust
2010-10-30 21:29 ` Brian J. Murrell
2010-10-30 21:41 ` Trond Myklebust
2010-10-30 21:46 ` Brian J. Murrell
2010-10-30 22:22 ` Trond Myklebust
2010-11-10 13:43 ` Brian J. Murrell
2010-11-11 5:19 ` Trond Myklebust
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=1288461151.3238.9.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=brian@interlinx.bc.ca \
--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;
as well as URLs for NNTP newsgroup(s).