From: Benny Halevy <bhalevy@tonian.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: "Welch, Brent" <welch@panasas.com>,
"Bhamare, Sachin" <sbhamare@panasas.com>,
"Adamson, Andy" <William.Adamson@netapp.com>,
Andy Adamson <androsadamson@gmail.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"<linux-nfs@vger.kernel.org>" <linux-nfs@vger.kernel.org>,
"Huang, James" <jhuang@panasas.com>
Subject: Re: [PATCH 2/3] NFSv4.1 mark layout when already returned
Date: Mon, 11 Jun 2012 17:04:31 +0300 [thread overview]
Message-ID: <4FD5FAEF.5040004@tonian.com> (raw)
In-Reply-To: <4FD5CBF6.6030800@panasas.com>
On 2012-06-11 13:44, Boaz Harrosh wrote:
> On 06/11/2012 12:56 PM, Benny Halevy wrote:
>
>>
>> It will for recovering files striped with RAID as the LAYOUTRETURN
>> provides the server with a reliable "commit point" where it knows
>> exactly what was written successfully to each stripe and can make
>> the most efficient decision about recovering it (if needed).
>>
>> Allowing I/O to the stripe post LAYOUTRETURN may result in data
>> corruption due to parity inconsistency.
>>
>
>
> The fact of the matter is that we - object guys - Which care about
> LAYOUTRETURN the most, have neglected to notice and fix the current
> situation which is even worse than After Andy's patch. Which will
> send multiple LAYOUTRETURNs on the same layout, and might still
> continue IO on returned layouts.
>
> Thanks Andy for testing and highlighting the current problem,
> I will prioritized this development internally at Panasas and
> will work on a solution ASAP. I hope one that will satisfy
> all.
>
> Basically my plan is to postpone the LAYOUTRETURN send to
> when the segment is last referenced, if a flag was set to
> do so, and make sure reference counting is done proper, so
> after flag set the last IO_done will send the LAYOUTRETURN.
>
> If that is OK with all I hope?
Sounds OK to me. Thanks!
Benny
>
>> Benny
>>
>
>
> Thanks
> Boaz
>
next prev parent reply other threads:[~2012-06-11 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 17:19 [PATCH 1/3] NFSv4.1 do not call LAYOUTRETURN when there are no legs andros
2012-06-01 17:19 ` [PATCH 2/3] NFSv4.1 mark layout when already returned andros
2012-06-02 22:51 ` Boaz Harrosh
2012-06-05 13:36 ` Adamson, Andy
2012-06-05 13:47 ` Andy Adamson
2012-06-05 14:54 ` Boaz Harrosh
2012-06-05 19:22 ` Andy Adamson
2012-06-05 20:49 ` Boaz Harrosh
2012-06-11 9:56 ` Benny Halevy
2012-06-11 10:44 ` Boaz Harrosh
2012-06-11 14:04 ` Benny Halevy [this message]
2012-06-11 14:21 ` Adamson, Andy
2012-06-11 14:51 ` Boaz Harrosh
2012-06-11 15:41 ` Adamson, Andy
2012-06-11 16:14 ` Boaz Harrosh
2012-06-11 15:08 ` Adamson, Andy
2012-06-11 15:38 ` Benny Halevy
2012-06-11 15:52 ` Adamson, Andy
2012-06-11 16:07 ` Boaz Harrosh
2012-06-11 15:59 ` Boaz Harrosh
2012-06-01 17:19 ` [PATCH 3/3] NFSv4.1 fence all layouts with file layout data server connection errors andros
2012-06-02 22:33 ` Boaz Harrosh
2012-06-04 13:49 ` Adamson, Andy
2012-06-02 23:00 ` [PATCH 1/3] NFSv4.1 do not call LAYOUTRETURN when there are no legs Boaz Harrosh
2012-06-05 13:36 ` Adamson, Andy
2012-06-05 15:01 ` Boaz Harrosh
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=4FD5FAEF.5040004@tonian.com \
--to=bhalevy@tonian.com \
--cc=Trond.Myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=androsadamson@gmail.com \
--cc=bharrosh@panasas.com \
--cc=jhuang@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sbhamare@panasas.com \
--cc=welch@panasas.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).