From: David Brown <david.brown@hesbynett.no>
To: Guillaume Betous <guillaume.betous@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Best practice for setting up "ordinary" RAID
Date: Fri, 11 Oct 2013 11:28:38 +0200 [thread overview]
Message-ID: <5257C4C6.5080600@hesbynett.no> (raw)
In-Reply-To: <CAPbD+RcN-ze=+wP+46N_wkVWkhV_feNXtkyKAuxy-D4MQmRctQ@mail.gmail.com>
On 11/10/13 10:57, Guillaume Betous wrote:
>> Any read
>> error or drive failure during the rebuild and you're in trouble.
>
> That was exactly what happened to me ! A rebuild is of course a very
> big load and another failure becomes more probable.
>
>> With RAID 6 you can handle 2 drive failures at any time
>
> Understood. I'll definitely switch to RAID 6 :)
>
>> They are more complex, but not enough so to trouble any modern CPU - you
>> might have issues on a 386/486, but I doubt you'll see any difference on
>> an Atom.
On modern CPUs, the raid6 calculations run fast - and on servers you
often have at least one CPU core doing nothing anyway.
The only slow part of raid6 calculations is when you have to read data
when there are two missing disks. But reading slowly with raid6 beats
no data at all with raid5!
Partial stripe writes (RMW writes) can be faster with raid5 than with
raid6, although I gather this has been under improvement recently.
(I've lost track of the status of these changes.) Usually, it is a
small price to pay.
>
> Ok. Maybe I should update French version of Wikipedia RAID article :)
> I'll test by myself.
> For now (RAID 5), on rebuild, it's about 30MB/s. On reading, it's
> about 90MB/s (direct access to /dev/md127, not read from FS).
>
> gUI
>
next prev parent reply other threads:[~2013-10-11 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 6:10 Best practice for setting up "ordinary" RAID Guillaume Betous
2013-10-11 6:35 ` Mikael Abrahamsson
2013-10-11 6:52 ` Guillaume Betous
2013-10-11 7:03 ` Mikael Abrahamsson
2013-10-11 7:14 ` Guillaume Betous
2013-10-11 7:19 ` Mikael Abrahamsson
2013-10-11 8:58 ` Guillaume Betous
2013-10-11 8:15 ` Robin Hill
2013-10-11 8:57 ` Guillaume Betous
2013-10-11 9:28 ` David Brown [this message]
2013-10-11 7:05 ` Adam Goryachev
2013-10-11 9:31 ` David Brown
2013-10-11 9:53 ` Guillaume Betous
2013-10-11 14:04 ` David Brown
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=5257C4C6.5080600@hesbynett.no \
--to=david.brown@hesbynett.no \
--cc=guillaume.betous@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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