From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-nfs@vger.kernel.org
Subject: Re: Error: state manager failed on NFSv4 server linux with error 127
Date: Sat, 30 Oct 2010 13:59:22 -0400 [thread overview]
Message-ID: <1288461562.32627.151.camel@pc> (raw)
In-Reply-To: <1288461151.3238.9.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Sat, 2010-10-30 at 13:52 -0400, Trond Myklebust wrote:
>
> 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.
To be clear, the trace was only that of blocked processes (echo w
> /proc/sysrq-trigger). I'm not sure if we should have expected the
state recovery thread to have been included (i.e. it was blocked too).
> Did you over-edit the trace output, or was this really all?
Other than the usual post-show-blocked-state output, yes, this really
was all there was.
What does the state recovery thread look like in the process table so
that I can look for it next time?
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-10-30 17:59 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
2010-10-30 17:59 ` Brian J. Murrell [this message]
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=1288461562.32627.151.camel@pc \
--to=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 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.