From: Trond Myklebust <trond.myklebust@fys.uio.no>
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 16:24:46 -0400 [thread overview]
Message-ID: <1288470286.3238.17.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1288468435.32627.279.camel@pc>
On Sat, 2010-10-30 at 15:53 -0400, Brian J. Murrell wrote:
> On Sat, 2010-10-30 at 14:19 -0400, Trond Myklebust wrote:
> >
> > It will be running a process with a name of the form "<server IP
> > address>-manager", and will be running the function
> > nfs4_run_state_manager().
>
> I will keep an eye out for that the next time I see this problem.
>
> > BTW: Do you have the following patches applied?
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=b0ed9dbc24f1fd912b2dd08b995153cafc1d5b1c
> > and
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=ae1007d37e00144b72906a4bdc47d517ae91bcc1
>
> Nope.
>
> > They are not yet in the stable kernel series,
>
> Which would be why I don't have them. I am working with a 2.6.35
> kernel.
>
> > AFAIK, but are slated to
> > be merged soon.
>
> I take that mentioning them in this context means they would be good to
> have? Safe to apply to 2.6.35.4ish kernel?
Yes.
next prev parent reply other threads:[~2010-10-30 20:24 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
2010-10-30 18:19 ` Trond Myklebust
2010-10-30 19:53 ` Brian J. Murrell
2010-10-30 20:24 ` Trond Myklebust [this message]
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=1288470286.3238.17.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--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).