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 22:22:48 -0700	[thread overview]
Message-ID: <516E31A8.9030607@tigertech.com> (raw)
In-Reply-To: <20130417102052.20c40887@natsu>

On 4/16/13 9:20 PM, Roman Mamedov wrote:

> You do know there is no "voting" system in md, right?

Yes, but the question was "What do you do if you do a through check and
both drives claim a data block is valid and intact, but data differs?"
The implication was that the array has failed and you need to manually
reconstruct data, perhaps sector-by-sector.

Having three sources for a manual reconstruction outside of md reduces
the "someone with two clocks never knows what time it is" problem. With
three, you can make an informed guess about which one is wrong.

I'm not saying that this is the primary reason to use three disks in
RAID 1, because it's not. I've never needed to do sector-level recovery
of an array. The primary reason is so that you can withstand two
simultaneous disk failures, just as with RAID 6 vs. RAID 5.


> In general, you seem to be WAY too concerned about losing your RAID array;
> this sounds like you are someone who doesn't make backups and tries to use
> RAID as a replacement for them.

No, that's definitely not the case. We have backup systems in multiple
data centers, and our disaster recovery planning includes plane crashes
that destroy live servers and so on.

Many businesses require 100% availability. Losing an array on a server
means downtime and telling paying customers "we lost the new data you
stored since the last backup". Neither is acceptable if it's in any way
avoidable, even if the last backup was minutes ago. Like you, I can
easily recover from losing a couple of hours work, but my customers who
run online stores are less sanguine about such things.

By the way, I think I'm going to pin "you seem to be WAY too concerned
about losing your RAID array" up on my wall. That's wonderful, because
it's exactly how concerned I want to be.  ;-)

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


  reply	other threads:[~2013-04-17  5:22 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
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 [this message]
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=516E31A8.9030607@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.