linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Ronal Andadinata <randadinata@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm, bitmap and split-brain
Date: Tue, 6 Dec 2011 15:45:22 +1100	[thread overview]
Message-ID: <20111206154522.13235bf4@notabene.brown> (raw)
In-Reply-To: <4ED14BEF.2060301@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

On Sun, 27 Nov 2011 03:28:31 +0700 Ronal Andadinata <randadinata@gmail.com>
wrote:

> Hi,
> 
> I'm wondering, in the case of raid1 array with internal bitmap, it goes 
> like this :
> 1. Machine A has 1 raid1 array with Disk1 dan Disk2
> 2. Dettach Disk2 from Machine A, put it on Machine B
> 3. Machine A runs normally, Machine B runs on normally on different place.
> 4. Detach Disk2 from Machine B, put it back on Machine A, re-add Disk2 
> to md1
> 
> If this were raid1 without bitmap, Disk2 will be overwritten from 
> scratch with contents of Disk1, what happen if the array has bitmap ? 
> Would there be partial sync ? Would the two disk be identical with only 
> using partial sync ?

It might fail to re-add, or it might do a partial resync and probably leave
the two devices different so corruption would likely appear.

Just don't do this.  If you want to use disk2 on a different machine,
assemble it with 
   --update=uuid
the first time so it gets a different uuid and can never become confused with
the old array.

NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2011-12-06  4:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 20:28 mdadm, bitmap and split-brain Ronal Andadinata
2011-12-06  4:45 ` 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=20111206154522.13235bf4@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=randadinata@gmail.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).