From: NeilBrown <neilb@suse.de>
To: Ming Lei <Ming.Lei@riverbed.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: question about bitmap for raid6
Date: Tue, 11 Sep 2012 09:07:48 +1000 [thread overview]
Message-ID: <20120911090748.59087250@notabene.brown> (raw)
In-Reply-To: <2CE44BD3DBCF9541909CCB42F11CA39284A942@SFO1EXC-MBXP06.nbttech.com>
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
On Mon, 10 Sep 2012 16:43:14 +0000 Ming Lei <Ming.Lei@riverbed.com> wrote:
> Neil,
>
> How about the other scenario: I plug out a drive and put aside for a while and put it back to the same machine with bitmap enabled for the raid6 array? Does it do full-recovery or fast resync?
If the array has been degraded that whole time, it will do a fast resync.
>
> I noticed either md superblock or bitmap superblock has events recorded and I guess it may be used to identify the up-to-date drive or the old drive put back again.
Correct.
NeilBrown
>
> Thanks
> Ming
>
> -----Original Message-----
> From: NeilBrown [mailto:neilb@suse.de]
> Sent: Sunday, September 09, 2012 3:51 PM
> To: Ming Lei
> Subject: Re: question about bitmap for raid6
>
> On Sat, 8 Sep 2012 21:07:46 +0000 Ming Lei <Ming.Lei@riverbed.com> wrote:
>
> > Hi Neil,
> >
> > We use 2.6.32 in house and most recently we found something bad happen when we turn on bitmap for raid6 array. Let me ask a question to help me to understand our situation.
> >
> > Say I have two hardware identical PCs(name them A and B) running with the same linux distribution. Both box has an raid6 array assmeblying 7 drives with internal bitmap. If I yank out one drive from PC B to make this drive slot empty, and then yank out a drive from PC A and move it to PC B, would md driver force the raid6 array on PC B rebuild(take a long time) or just do resync(very short time)? What's the condition on bitmap code to check if it is really the drive I just pull out from the same machine or it is the drive pulled out from different machine?
> >
> > Thanks
> > Ming
>
> PC B would not do anything to drive that you moved from PC A until you add it as a spare. Then it will perform a complete rebuild of the missing device to the new device. It will not do a partial recovery.
>
> 'md' knows it is a device from a different array because the 'uuid' stored in the metadata is different.
> If you managed to create two arrays on two different PCs which both had the same UUID, then you could definitely get strange data corruption happening, but that is very unlikely.
>
> NeilBrown
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-09-10 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2CE44BD3DBCF9541909CCB42F11CA39284A4F5@SFO1EXC-MBXP06.nbttech.com>
[not found] ` <20120910085035.3fe12f99@notabene.brown>
2012-09-10 16:43 ` FW: question about bitmap for raid6 Ming Lei
2012-09-10 23:07 ` 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=20120911090748.59087250@notabene.brown \
--to=neilb@suse.de \
--cc=Ming.Lei@riverbed.com \
--cc=linux-raid@vger.kernel.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 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).