All of lore.kernel.org
 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: Wed, 17 Apr 2013 11:26:10 +0200	[thread overview]
Message-ID: <516E6AB2.3050701@hesbynett.no> (raw)
In-Reply-To: <alpine.DEB.2.00.1304170952280.23668@uplift.swm.pp.se>

On 17/04/13 09:56, Mikael Abrahamsson wrote:
> On Tue, 16 Apr 2013, David Brown wrote:
> 
>> you are going to have terrible RMW performance for small writes. 
>> However, as
> 
> As I said, I don't have problem with lower performance. My workload is
> write once and few, read many. If the performance is approximately the
> approximately the same as a 10 drive RAID-6, but with double the
> storage, I'm fine.

I would expect read performance for triple-parity raid to be similar to
Raid5 or Raid6 - i.e., you get good striped performance, especially for
large files as they are spread over many spindles.  Of course, since
triple-parity md raid does not yet exist, that's just theoretical...

> 
>> 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.
> 
> Well, I run RAID6+spare. I'd rather run a triple parity drive unless the
> write performance penalty is huge.
> 

It's encouraging to hear people are interested in this.  But before it
can be implemented, there has to be someone with an understanding of
Linux md raid who can implement it.  I know the maths involved, but I
have no experience with Linux kernel work (I work with embedded systems
- while I use the same programming language as the kernel, it's a very
different style of programming).


  reply	other threads:[~2013-04-17  9:26 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
2013-04-17  7:56     ` Mikael Abrahamsson
2013-04-17  9:26       ` David Brown [this message]
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=516E6AB2.3050701@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 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.