From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trondmy@primarydata.com>,
"jlayton\@poochiereds.net" <jlayton@poochiereds.net>,
"linux-nfs\@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: "hch\@infradead.org" <hch@infradead.org>
Subject: Re: Confused by pnfs LAYOUTRETURN - seeking clarity.
Date: Wed, 08 Mar 2017 07:09:26 +1100 [thread overview]
Message-ID: <87wpc0j1c9.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1488847700.2913.1.camel@primarydata.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Tue, Mar 07 2017, Trond Myklebust wrote:
> Hi Neil,
>
> On Mon, 2017-03-06 at 14:54 +1100, NeilBrown wrote:
...
>>
>> So the Netapp filer is clearly doing the wrong thing, as we doesn't
>> send
>> CB_LAYOUTRECALL. But I'm far from convinced that Linux is doing the
>> right thing by replying NFS4ERR_NOMATCHING_LAYOUT.
>>
>> However, I'm not going to try to "fix" anything here. Hopefully we
>> can
>> manage to stumble forward.
>>
>
> Please see RFC5661, Section 12.5.5.1 https://tools.ietf.org/html/rfc566
> 1#section-12.5.5.1
>
> That section has a full documentation of what the server should
> interpret NFS4ERR_NOMATCHING_LAYOUT to mean, and should explain why the
> Linux client behaviour is quite correct w.r.t. the spec.
> There are a couple of errata to consider too, but they mainly try to
> nail down the expected behaviour for a couple of corner cases.
Thanks for that. The last too sentences to suggest that
NFS4ERR_NOMATCHING_LAYOUT isn't really an error, and the whole
discusses how the server and client can reasonably have different
understandings of the current set of layouts.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-03-07 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 21:24 Confused by pnfs LAYOUTRETURN - seeking clarity NeilBrown
2017-03-03 15:16 ` Christoph Hellwig
2017-03-03 19:25 ` Jeff Layton
2017-03-06 3:54 ` NeilBrown
2017-03-07 0:48 ` Trond Myklebust
2017-03-07 20:09 ` NeilBrown [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=87wpc0j1c9.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=hch@infradead.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@primarydata.com \
/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).