From: Drew <drew.kay@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: migrating from RAID5 to RAID10
Date: Thu, 10 Jun 2010 15:21:27 -0700 [thread overview]
Message-ID: <AANLkTimW4IMO55vL-icTcpkcg9d10dK13yIGu4XZbrQQ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim3vrtAfgzY87IAmP6mY9PNiYiQZ1LyuqWHisiD@mail.gmail.com>
>> No, it is not degraded, it's a clean 2-drive RAID5. I know it doesn't
>> make much sense as it is ;-) the intent was to grow the array later,
>> relying on mdadm's grow feature. Right now, I'm guessing that it
>> operates like a RAID1 for all practical purposes.
>
> Actually No. If it is RAID-5 as you claim, then currently it is
> effectively a RAID-0.
>
> RAID-5 is Striping with Distributed Parity and requires a *minimum* of
> 3 disks. Two disks, regardless of how you got there, is considered a
> degraded state.
Actually, I need to retract those statements. A clean two disk RAID-5
array can be created and is actually very similar to a RAID-1 array.
From this thread: http://ubuntuforums.org/archive/index.php/t-566803.html
---
If you're using just 2 disks in a non-degraded setup, then you'll have
the following structure
Drive1 Drive2
Block1: A1 P1
Block2: P2 B1
Block3: C1 P3
Block4: P4 D1
In this case, you're parity blocks will actually be identical to your
non-parity blocks. This is because P1 is calculated as P1 = A1 XOR ??
Since there is no other block to XOR your bits with, md falls back to
?? = 0, and we all know that the XOR of 0 is the identity. That is, P1
= A1 XOR 0 == A1
---
I stand corrected. :-)
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
--
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
next prev parent reply other threads:[~2010-06-10 22:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:11 migrating from RAID5 to RAID10 Gilad Arnold
2010-06-10 18:52 ` Roman Mamedov
2010-06-10 19:58 ` Gilad Arnold
2010-06-10 22:11 ` Drew
2010-06-10 22:21 ` Drew [this message]
2010-06-10 22:30 ` Gilad Arnold
2010-06-10 22:26 ` Gilad Arnold
2010-06-16 15:54 ` Bill Davidsen
2010-06-16 18:30 ` Gilad Arnold
2010-06-16 20:15 ` Gilad Arnold
2010-06-17 1:59 ` Bill Davidsen
2010-06-16 21:26 ` Neil Brown
2010-06-17 17:44 ` Gilad Arnold
2010-06-17 22:30 ` Neil Brown
2010-06-18 8:40 ` Keld Simonsen
2010-06-21 22:09 ` Neil Brown
2010-06-17 22:46 ` Gilad Arnold
2010-06-18 2:39 ` Neil Brown
2010-06-18 4:01 ` Gilad Arnold
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=AANLkTimW4IMO55vL-icTcpkcg9d10dK13yIGu4XZbrQQ@mail.gmail.com \
--to=drew.kay@gmail.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).