From: Michael Evans <mjevans1983@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Neil Brown <neilb@suse.de>,
Guy Watkins <linux-raid@watkins-home.com>,
Greg Freemyer <greg.freemyer@gmail.com>,
Mark Knecht <markknecht@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: What RAID type and why?
Date: Sun, 7 Mar 2010 12:40:24 -0800 [thread overview]
Message-ID: <4877c76c1003071240t6814248eqd63f391bc278aee8@mail.gmail.com> (raw)
In-Reply-To: <877hpoqoob.fsf@frosties.localdomain>
On Sun, Mar 7, 2010 at 4:52 AM, Goswin von Brederlow <goswin-v-b@web.de> wrote:
> Neil Brown <neilb@suse.de> writes:
>
>> On Sat, 06 Mar 2010 18:17:44 -0500
>> "Guy Watkins" <linux-raid@watkins-home.com> wrote:
>>
>>> }
>>> } At a minimum I would build a 3-disk raid 6. raid 6 does a lot of i/o
>>> } which may be a problem.
>>>
>>> If he only needs 3 drives I would recommend RAID1. Can still loose 2 drives
>>> and you don't have the RAID6 I/O overhead.
>>>
>>
>> and as md/raid6 requires at least 4 drives, RAID1 is not just the best
>> solution to survive two failures on a 3-device array, it is the only solution.
>>
>> NeilBrown
>
> Except that there also is raid10 with 3 mirrors. :)
>
> MfG
> Goswin
>
> PS: Why doesn't raid6 still not allow 3 drives for the special case of
> converting raid1 -> raid6?
>
>
> --
> 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
>
That should be obvious:
Possible stripes:
Start:
1, 1, 1;
2, 2, 2;
'raid6' overtake...
1, q, Q;
2, q, Q;
'raid6' overtake with missing;
1, (missing 2), q, Q;
3, (missing 4), q, Q;
In the first overtake case you have the requirement of generating 200%
parity, which probably won't work for the algorithm and is a silly
idea in general since it's computationally far less expensive to store
another copy of either form of data instead.
In the second you're gaining the space of a second disk at the cost of
being already degraded; why not just go for raid 5 instead?
You can overtake raid5 later with raid6 if you add more devices.
--
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-03-07 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 22:02 What RAID type and why? Mark Knecht
2010-03-06 22:33 ` Greg Freemyer
2010-03-06 23:05 ` Mark Knecht
2010-03-07 0:38 ` Keld Simonsen
2010-05-10 15:20 ` Matt Garman
2010-05-10 15:34 ` Mark Knecht
2010-03-06 23:17 ` Guy Watkins
2010-03-06 23:51 ` Mark Knecht
2010-03-08 20:05 ` Bill Davidsen
2010-03-06 23:56 ` Michael Evans
2010-03-07 2:21 ` Neil Brown
2010-03-07 8:06 ` Keld Simonsen
2010-03-07 8:10 ` Guy Watkins
2010-03-07 8:22 ` 'Keld Simonsen'
2010-03-07 10:09 ` Michael Evans
2010-03-07 12:52 ` Goswin von Brederlow
2010-03-07 20:40 ` Michael Evans [this message]
2010-03-10 17:47 ` Goswin von Brederlow
2010-03-11 10:44 ` Michael Evans
2010-03-06 23:03 ` Asdo
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=4877c76c1003071240t6814248eqd63f391bc278aee8@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=goswin-v-b@web.de \
--cc=greg.freemyer@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=linux-raid@watkins-home.com \
--cc=markknecht@gmail.com \
--cc=neilb@suse.de \
/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).