All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Robert L Mathews <lists@tigertech.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Use RAID-6!
Date: Wed, 17 Apr 2013 01:06:00 -0500	[thread overview]
Message-ID: <516E3BC8.5080909@hardwarefreak.com> (raw)
In-Reply-To: <516E24C8.9080803@tigertech.com>

On 4/16/2013 11:27 PM, Robert L Mathews wrote:

> I avidly read the details of every RAID 5 [and 6] disaster on the list,
> and almost every one would be trivially easy to fix under RAID 1, with
> no risk of complete data loss. It's heartbreaking.

I do read most of them as well.  But mirrors simply don't scale in
either capacity or performance and thus aren't suitable.  If one needs a
4TB+ filesystem today or more than combined ~150MB/s streaming write
throughput one must use one of:

1.  RAID10
2.  RAID0 over RAID1 pairs/triples
3.  A linear concat over pairs/triples w/XFS
4.  RAID5 or RAID6

Each of these is most suitable for only subset of workloads, but all of
them can scale to more than 4TB, whereas RAID1 cannot.  When
SATA4/SAS1200 arrive offering 1.2GB/s interface rate, and SSDs hit 2-4TB
capacity at reasonable prices, then I think you'll see more straight
RAID1 being used in more of the systems that don't need any more total
capacity.  But as many servers will always need more than this and will
still use rust, striped/concatenated arrays will be with us for quite
some time.

And BTW, regarding your triplets setup, if you want to do that right
according to your philosophy, then you need a dedicated SAS/SATA
controller for each drive, each controller being of a different
make/model with different firmware.  The old UNIX/Netware "duplexing"
strategy but triplexing in this case.  But I doubt you're doing this.
All 3 are probably connected to the single motherboard down SATA
controller.

-- 
Stan


  parent reply	other threads:[~2013-04-17  6:06 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
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 [this message]
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=516E3BC8.5080909@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@tigertech.com \
    /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.