From: "peng.hse" <peng.hse@xtaotech.com>
To: dillaman@redhat.com
Cc: Sage Weil <sweil@redhat.com>, Josh Durgin <jdurgin@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: problems to protect rbd from mutiple simultaneous mapping
Date: Tue, 7 Mar 2017 10:16:11 +0800 [thread overview]
Message-ID: <58BE17EB.1050105@xtaotech.com> (raw)
In-Reply-To: <CA+aFP1AO1DkYEVSfzHLk=dHSn8cSPE1c3+aWNAzQwwmsOuBsvA@mail.gmail.com>
what i mean is : the step-1's IO from node1 was received by the OSDs
before the blacklist barrier,
however, still under progress after the blacklist barrier, which might
overwrite the data by node2 and
corrupt our data.
How do we avoid this situation?
On 2017年03月07日 07:47, Jason Dillaman wrote:
> On Mon, Mar 6, 2017 at 9:08 AM, peng.hse <peng.hse@xtaotech.com> wrote:
>> 3. assuming the step-1 outstanding IO and step-2 IO targeted the same area
>> of the fs metadata
>> on the rbd devices. step-2 successfully persist the data and reply to
>> client.
>> then, the following laggy IO from step-1 might override and corrupt what
>> we have written in step-2.
>>
>> so, how do we prevent this kind of corruption happening?
> ... but in step (2) you successfully blacklisted the client on node1
> (i.e. it is not allowed to talk to the OSDs). Therefore, node1 cannot
> overwrite any data written by node2.
>
next prev parent reply other threads:[~2017-03-07 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:08 problems to protect rbd from mutiple simultaneous mapping peng.hse
2017-03-06 23:47 ` Jason Dillaman
2017-03-07 2:16 ` peng.hse [this message]
2017-03-07 2:26 ` Jason Dillaman
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=58BE17EB.1050105@xtaotech.com \
--to=peng.hse@xtaotech.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=jdurgin@redhat.com \
--cc=sweil@redhat.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 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.