From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jonas Jonsson <jonas@websystem.se>
Cc: nfs@lists.sourceforge.net, Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Problem with NFS4, Error: state recovery failed on NFSv4 server 192.168.0.1 with error 121
Date: Mon, 24 Sep 2007 18:20:26 -0400 [thread overview]
Message-ID: <20070924222026.GP26387@fieldses.org> (raw)
In-Reply-To: <20070924220247.GO26387@fieldses.org>
On Mon, Sep 24, 2007 at 06:02:47PM -0400, bfields wrote:
> OK, thanks! Looks like it starts out fairly normally, then at packet
> 824 it gets into this SETCLIENTID->NFS4ERR_RESOURCE loop. I'm not sure
> how that happened.
>
> I'm a little unclear whether RESOURCE is supposed to be a temporary
> error or not, but in either case retrying it indefinitely with no delay
> is probably a bad idea. But I guess that's not the bug. OK, I'll try
> to figure out what lead up to that....
Oh, good grief, we're lame. Could you check your .config--is it
possible you have CONFIG_CRYPTO_MD5 turned off? If so, could you verify
that turning it on fixes the problem?
The recovery code is being silly and returning RESOURCE if it can't load
that crypto module. Current upstream doesn't allow building v4 without
MD5, so you probably won't be able to reproduce the problem on the
latest kernel.
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-09-24 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 17:45 Problem with NFS4, Error: state recovery failed on NFSv4 server 192.168.0.1 with error 121 Jonas Jonsson
2007-09-17 17:07 ` Trond Myklebust
2007-09-17 17:12 ` Trond Myklebust
2007-09-17 19:12 ` Jonas Jonsson
2007-09-17 19:57 ` Trond Myklebust
2007-09-17 20:25 ` Jonas Jonsson
2007-09-20 9:52 ` Jonas Jonsson
2007-09-21 17:41 ` Trond Myklebust
2007-09-22 18:52 ` J. Bruce Fields
2007-09-24 21:19 ` Jonas Jonsson
2007-09-24 22:02 ` J. Bruce Fields
2007-09-24 22:20 ` J. Bruce Fields [this message]
2007-09-25 12:14 ` Jonas Jonsson
2007-09-25 15:20 ` J. Bruce Fields
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=20070924222026.GP26387@fieldses.org \
--to=bfields@fieldses.org \
--cc=jonas@websystem.se \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.