From: Phil Turmel <philip@turmel.org>
To: maurice <mhilarius@gmail.com>
Cc: Iordan Iordanov <iordan@cdf.toronto.edu>, linux-raid@vger.kernel.org
Subject: Re: Looking for the best way to do this
Date: Thu, 23 Jun 2011 18:55:00 -0400 [thread overview]
Message-ID: <4E03C444.6060406@turmel.org> (raw)
In-Reply-To: <4E03B8DB.7010607@gmail.com>
Hi maurice,
On 06/23/2011 06:06 PM, maurice wrote:
> On 6/23/2011 1:23 PM, Iordan Iordanov wrote:
>> Hi Maurice,
>>
>> On 06/21/11 14:13, maurice wrote:
>>> Add 3rd disk to make a 3 disk RAID1
>>> Make a RAID10, missing one disk.
>>
>> Perhaps I misunderstand your supposition, and if I do, please correct me. RAID10 with mdadm does not require a minimum of 4 disks.
> Yes, that was my understanding.
>
>> For example, mdadm can do RAID10 with 2 copies on 3 disks or RAID10 with 3 copies on 3 disks, yielding the equivalent of RAID1 in terms of data security. It is not confined to mirroring two pairs of disks and then striping across them as is the "conventional" way of doing RAID10.
> Yes, I understand the principle.
>>
>> You can read the man-page of mdadm, where the options for "layout" of RAID10 are discussed. Pay particular attention to the end of the "--layout" option explanation.
>
> What I do NOT know is the following:
> A) Which is more RELIABLE: R1 with 3 disks or R10 with 3 disks.
R1 with 3 disks is three copies of all sectors. R10 with three disks can be either two copies of each sector or three copies. A two-copy layout would have capacity equal to 1.5 * the member disk size. For reliability, three copies is better than two copies. R10 and R1 use different algorithms, so you will have different performance pros and cons.
> B) HOW to create either the 3 disk R1 or R10, assuming an existing 2 disk R1.
You can "--grow" the number of disks (copies) in an R1 while running. R10 does not (yet) support layout or capacity changes, whether running or not. So if you want R10, you'll have to start from scratch.
If you are willing to give up your redundancy temporarily, you could create a degraded R10 from the new drive and one of the existing drives, copy the partition from the remaining drive in the R1, stop and destroy the R1, then add that disk into the R10.
Phil
next prev parent reply other threads:[~2011-06-23 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 18:13 Looking for the best way to do this maurice
2011-06-23 1:20 ` Leslie Rhorer
2011-06-23 19:23 ` Iordan Iordanov
2011-06-23 22:06 ` maurice
2011-06-23 22:55 ` Phil Turmel [this message]
[not found] ` <4E03CBC3.1080001@gmail.com>
2011-06-23 23:41 ` Phil Turmel
2011-06-24 16:17 ` Iordan Iordanov
2011-06-24 16:35 ` maurice
2011-06-24 16:59 ` Iordan Iordanov
2011-06-24 17:11 ` maurice
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=4E03C444.6060406@turmel.org \
--to=philip@turmel.org \
--cc=iordan@cdf.toronto.edu \
--cc=linux-raid@vger.kernel.org \
--cc=mhilarius@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 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.