Linux RAID subsystem development
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Use RAID-6!
Date: Tue, 16 Apr 2013 22:01:18 +0200	[thread overview]
Message-ID: <516DAE0E.5080209@hesbynett.no> (raw)
In-Reply-To: <alpine.DEB.2.00.1304161905150.23668@uplift.swm.pp.se>

On 16/04/13 19:09, Mikael Abrahamsson wrote:
> On Tue, 16 Apr 2013, Roy Sigurd Karlsbakk wrote:
>
>> Also, maybe this should be on an FAQ/RAID tutorial somewhere?
>
> Question is, where should it be put so that people read it and actually
> understand it.
>
> This article is from 2007:
>
> <http://www.zdnet.com/blog/storage/why-raid-5-stops-working-in-2009/162>
>
> I've had people argue with me that the above article is wrong, but I
> never udnerstood their logic. To me it makes perfect sense and I always
> go RAID6.
>
> I also think the work having more than 2 parity drives was very
> promising. I'd rather have a 20 drive volume with 4 parity drives than
> to LVM together two 10 drive RAID6:es (apart from obvious performance
> penalties).
>

Raid calculations for a third parity are noticeably more time-consuming 
than for the second parity of Raid6.  And with a bigger array with lots 
of drives, you are going to have terrible RMW performance for small 
writes.  However, as the multi-threaded scaling of Raid5 and Raid6 
improves and makes its way into distro's standard kernels, it's going to 
be more realistic - especially for machines with plenty of cores and 
lots of RAM for stripe caches.

I hope triple parity raid will make it into the kernel at some point. 
I've done the main part of the maths involved, but not had the time to 
work it into anything resembling real code.  I don't know if I 
personally will ever make it into working code - but if anyone else is 
at all interested in doing so, then I will certainly help with the maths.

I am not sure there is much real-world need of triple parity raid for 
normal arrays - even with better cpu scaling, it would still be a lot 
slower than two raid6 arrays LVM'ed together.  I foresee it's main use 
as a temporary measure during array maintenance.  For example, if you 
have a raid6 and you want to swap out the drives for bigger ones, then 
you could temporarily add an extra drive for a third parity using a 
non-symmetrical layout.  Once this extra drive is synced, then you can 
step through the other drives doing a replace-and-resync, knowing that 
you still have the double parity safety.  Then at the end of the process 
you drop the third parity again.

Quad parity has some limitations, especially if you want to keep the 
first 3 parities compatible with triple parity.  In particular, you are 
limited to 21 data disks.  There are, of course, ways to handle even 
greater parity counts - but the cost in complexity and speed is 
considerable.



  parent reply	other threads:[~2013-04-16 20:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 16:44 Use RAID-6! Roy Sigurd Karlsbakk
2013-04-16 17:09 ` Mikael Abrahamsson
2013-04-16 17:25   ` Roy Sigurd Karlsbakk
2013-04-16 20:01   ` David Brown [this message]
2013-04-17  7:56     ` Mikael Abrahamsson
2013-04-17  9:26       ` David Brown
2013-04-16 19:52 ` Robert L Mathews
2013-04-16 20:05   ` Carsten Aulbert
2013-04-16 20:19     ` Roman Mamedov
2013-04-16 22:44     ` Robert L Mathews
2013-04-17  0:20       ` Ben Bucksch
2013-04-17  1:35         ` Adam Goryachev
2013-04-17  4:27           ` Robert L Mathews
2013-04-17  4:45             ` Adam Goryachev
2013-04-17  6:06             ` Stan Hoeppner
2013-04-17 11:13           ` Ben Bucksch
2013-04-17 11:32             ` Adam Goryachev
2013-04-17 11:51               ` Ben Bucksch
2013-04-17 17:50                 ` Roy Sigurd Karlsbakk
2013-04-17  3:32         ` Robert L Mathews
2013-04-17  4:20       ` Roman Mamedov
2013-04-17  5:22         ` Robert L Mathews
2013-04-17 17:27   ` Roy Sigurd Karlsbakk
2013-04-16 23:42 ` md dropping disks too early (was: Use RAID-6!) Ben Bucksch
2013-04-17  8:00   ` Mikael Abrahamsson
2013-04-17 10:57     ` md dropping disks too early Ben Bucksch
2013-04-17 15:03       ` Keith Keller
2013-04-17 18:09       ` Roy Sigurd Karlsbakk

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=516DAE0E.5080209@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=linux-raid@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    --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