All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert L Mathews <lists@tigertech.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Use RAID-6!
Date: Tue, 16 Apr 2013 15:44:03 -0700	[thread overview]
Message-ID: <516DD433.50100@tigertech.com> (raw)
In-Reply-To: <516DAF21.5040409@aei.mpg.de>

On 4/16/13 1:05 PM, Carsten Aulbert wrote:

> The problem I find with RAID1 is that it won't protect you against
> silent corruptions (same as RAID5). What do you do if you do a through
> check and both drives claim a data block is valid and intact, but data
> differs? Do you trust disk1 or disk2?

That's partly why we use three-disk arrays instead of two-disk.

But as you say, this general issue is a problem with RAID 5 too. We plan
to switch to Btrfs as soon as doing so is wise.

In the meantime, I'd rather risk this problem than the endless reports
of complete array failures that appear on the list with RAID 5 and even
RAID 6 (a recent topic, I note, was "multiple disk failures in an md
raid6 array"). I almost never see anyone reporting complete loss of a
RAID 1 array.

The fundamental difference between RAID 1 and other levels seems to be
that the usefulness of an individual array member doesn't rely on the
state of any other member. This vastly reduces the impact of failures on
the overall system. After using mdadm with various RAID levels since
2002 (thanks, Neil), I'm convinced that RAID 1 is by its very nature far
less fragile than any other scheme. This belief is sadly reinforced
almost every week by a new tale of woe on the mailing list.

-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

  parent reply	other threads:[~2013-04-16 22:44 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 [this message]
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=516DD433.50100@tigertech.com \
    --to=lists@tigertech.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 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.