From: Boaz Harrosh <bharrosh@panasas.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Andy Adamson <androsadamson@gmail.com>, NFSv4 <nfsv4@ietf.org>,
"Adamson, Andy" <William.Adamson@netapp.com>,
NFS list <linux-nfs@vger.kernel.org>,
Benny Halevy <bhalevy@tonian.com>
Subject: Re: RFC 5661 LAYOUTRETURN clarification.
Date: Tue, 12 Jun 2012 01:18:07 +0300 [thread overview]
Message-ID: <4FD66E9F.708@panasas.com> (raw)
In-Reply-To: <1339441159.19775.25.camel@lade.trondhjem.org>
On 06/11/2012 09:59 PM, Myklebust, Trond wrote:
> On Mon, 2012-06-11 at 21:40 +0300, Boaz Harrosh wrote:
>
>> And again, please explain why do you want it. What is wrong with the
>> case we all agree with? ie: "Client can not call LAYOUTRETURN until
>> all in-flight RPCs return, with or without an error"
>
> Who "agreed" to this? This would mean that if the DS goes down, we can't
> ever send LAYOUTRETURN which is patently wrong.
>
"DS goes down" is under the above "RPC return an error" the error condition
of an RPC is well defined.
>From what of my words did you understand that I said
"we can't ever send a LAYOUTRETURN"
If my English is wrongly worded. Which is perfectly possible. Please correct
me so I can learn. Did you honestly think that's what I meant?
I meant we all agree, that this case is covered by RFC. That is - no one would
accuse a client who does that, as violating the RFC.
And again my question. The motivation?
Thanks
Boaz
next prev parent reply other threads:[~2012-06-11 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHVgHyUpM0rQWqO5-id+FohPKm1Lk=kkekf7HqzpfKcfvxx23A@mail.gmail.com>
2012-06-11 18:40 ` RFC 5661 LAYOUTRETURN clarification Boaz Harrosh
2012-06-11 18:59 ` Myklebust, Trond
2012-06-11 22:18 ` Boaz Harrosh [this message]
2012-06-11 22:31 ` Myklebust, Trond
2012-06-12 16:34 ` Welch, Brent
2012-06-11 19:02 ` [nfsv4] " david.noveck
2012-06-11 19:43 ` Myklebust, Trond
2012-06-11 20:11 ` [nfsv4] RFC 5661 write to DS clarification. (was: [nfsv4] RFC 5661 LAYOUTRETURN clarification) Myklebust, Trond
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=4FD66E9F.708@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=androsadamson@gmail.com \
--cc=bhalevy@tonian.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.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.