linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david@westcontrol.com>
To: linux-raid@vger.kernel.org
Subject: Re: from 2x RAID1 to 1x RAID6 ?
Date: Wed, 08 Jun 2011 11:38:56 +0200	[thread overview]
Message-ID: <isng0m$8c9$1@dough.gmane.org> (raw)
In-Reply-To: <4DEEBB66.7080802@nybeta.com>

On 08/06/2011 01:59, Thomas Harold wrote:
> On 6/7/2011 4:07 PM, Maurice Hilarius wrote:
>> On 6/7/2011 12:12 PM, Stefan G. Weichinger wrote:
>>> Greetings, could you please advise me how to proceed?
>>>
>>> On a server I have 2 RAID1-arrays, each consisting of 2 TB-drives:
>>>
>>> ..
>>>
>>> Now I would like to move things to a more reliable RAID6 consisting of
>>> all the four TB-drives ...
>>>
>>> How to do that with minimum risk?
>>>
>>> ..
>>> Maybe I overlook a clever alternative?
>>
>> RAID 10 is as secure, and risk free, and much faster.
>> And will cause much less CPU load.
>>
>
> Well, with both a pair of RAID1 arrays and a pair of RAID-10 arrays, you
> can lose 2 disks without losing data, but only if the right 2 disks fail.
>
> With RAID6, any two of the four can fail without data loss.
>

It /sounds/ like RAID6 is more reliable here because it can always 
survive a second disk failure, while with RAID10 you have only a 66% 
chance of surviving a second disk failure.

However, how often does a disk fail?  What is the chance of a random 
disk failure in a given space of time?  And how long will it go between 
one disk failing, and it being replaced and the array rebuilt?  If you 
figure out these numbers, you'll have the probability of losing your 
RAID10 array due to the second critical disk failing.

To pick some rough numbers - say you've got low reliability, cheap disks 
with a 500,000 hour MTBF.  If it takes you 3 days to replace a disk 
(over the weekend), and 8 hours to rebuild, you have a risk period of 80 
hours.  That gives you a 0.016% chance of having the second disk 
failing.  Even if you consider that a rebuild is quite stressful on the 
critical disk, it's not a big risk.

Compare that to the chance of losing data through other causes (fire, 
theft, user-error, motherboard failure, power supply problems, etc., 
etc.) and in reality the "higher risk" of RAID10 compared to RAID6 is a 
drop in the ocean.  RAID10 is /far/ from being the weak point in a 
typical server.

And you can also take into account that the disk usage patterns on RAID6 
are a lot more intensive and stressful on the disk than RAID10 - I would 
expect the lifetime of a RAID10 member disk to be much higher than that 
of a RAID6 member disk.

I don't have the statistics to prove it, but I am certainly happy to use 
RAID10 rather than RAID6 for our company servers.

Of course, I also have two backup servers on two different sites...

> (I still prefer RAID-10 over RAID-6 unless space is at an absolute
> premium. But for a four-disk setup, net disk space is the same and it's
> just a question of whether you want the speed of RAID-10 or the
> reliability of RAID-6.)



  parent reply	other threads:[~2011-06-08  9:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 18:12 from 2x RAID1 to 1x RAID6 ? Stefan G. Weichinger
2011-06-07 20:07 ` Maurice Hilarius
2011-06-07 23:59   ` Thomas Harold
2011-06-08  8:06     ` Stefan G. Weichinger
2011-06-08  9:38     ` David Brown [this message]
2011-06-08 10:11       ` John Robinson
2011-06-08 10:33         ` David Brown
2011-06-08 14:20           ` Phil Turmel
2011-06-08 14:42             ` Stefan G. Weichinger
2011-06-09 13:18           ` Nikolay Kichukov
2011-06-09 13:42             ` David Brown
2011-06-08  1:16 ` John Robinson
2011-06-08  8:16   ` Stefan G. Weichinger
2011-06-08  9:43 ` David Brown
2011-06-08 12:31   ` Stefan G. Weichinger

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='isng0m$8c9$1@dough.gmane.org' \
    --to=david@westcontrol.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).