From: Benjamin Coddington <Benjamin.Coddington@uvm.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] Don't convert NFS4ERR_RESOURCE to EREMOTEIO
Date: Wed, 04 Mar 2009 14:49:26 -0500 [thread overview]
Message-ID: <49AEDB46.5080905@uvm.edu> (raw)
In-Reply-To: <20090304193519.GC28951@fieldses.org>
In that case, maybe the unused test should be cleaned up to avoid
fooling any other administrators.
Shall I send along a patch removing the test in setclientid_confirm?
(Its also used in increment_seqid)
Ben
J. Bruce Fields wrote:
> On Wed, Mar 04, 2009 at 02:30:10PM -0500, Trond Myklebust wrote:
>> On Wed, 2009-03-04 at 14:01 -0500, J. Bruce Fields wrote:
>>> On Wed, Mar 04, 2009 at 01:42:30PM -0500, Benjamin Coddington wrote:
>>>> Fixes a test in nfs4_proc_setclientid_confirm() which allows the client
>>>> to retry an operation when the server returns NFS4ERR_RESOURCE, instead
>>>> of returning EREMOTEIO to the user.
>>> I remember being confused as to whether NFS4ERR_RESOURCE is transitory
>>> (hence worth being retried) or permanent (in which case retrying the
>>> identical compound won't help). The latter might happen if, for
>>> example, the particular sequence of compounds sent by the client was
>>> just too long or complicated for the server to handle.
>>>
>>> But rfc3530 doesn't explicitly limit NFS4ERR_RESOURCE to that case, and
>>> it appears that other clients:
>>>
>>> http://www.nfsv4.org/nfsv4-wg-archive-feb-03-feb-05/0747.html
>>>
>>> retry. That discussion isn't conclusive, though. Hm, and there's
>>> further discussion from Mike Eisler here:
>>>
>>> http://www.nfsv4-editor.org/cgi-bin/roundup/nfsv4/file7/comp-res.txt
>>>
>>> which suggests it was intended as a permanent error.
>>>
>>> What was the specific case where you hit this?
>> He says it was in SETCLIENTID_CONFIRM.
>>
>> AIX used to abuse the NFS4ERR_RESOURCE error in order to delay clients
>> while the server was doing some preparations for state recovery. They
>> argues that they couldn't use NFS4ERR_DELAY since it isn't listed as a
>> legal error for SETCLIENTID_CONFIRM in RFC3530,
>
> Oh, good grief, I'd forgotten that story. OK!--b.
>
>> and so they picked
>> NFS4ERR_RESOURCE. That would be a server bug...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-03-04 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 18:42 [PATCH] Don't convert NFS4ERR_RESOURCE to EREMOTEIO Benjamin Coddington
2009-03-04 18:57 ` Trond Myklebust
2009-03-04 19:01 ` J. Bruce Fields
2009-03-04 19:25 ` Benjamin Coddington
2009-03-04 19:33 ` J. Bruce Fields
2009-03-04 19:30 ` Trond Myklebust
[not found] ` <1236195010.7807.26.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-04 19:35 ` J. Bruce Fields
2009-03-04 19:49 ` Benjamin Coddington [this message]
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=49AEDB46.5080905@uvm.edu \
--to=benjamin.coddington@uvm.edu \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox