From: Roman Mamedov <rm@romanrm.ru>
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 10:20:52 +0600 [thread overview]
Message-ID: <20130417102052.20c40887@natsu> (raw)
In-Reply-To: <516DD433.50100@tigertech.com>
[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]
On Tue, 16 Apr 2013 15:44:03 -0700
Robert L Mathews <lists@tigertech.com> wrote:
> 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.
You do know there is no "voting" system in md, right?
If you imagine that all three disks are being read in parallel, and if one
returns bad data, it is automatically "overruled" by a majority vote from the
two other ones with correct data, that's not how it works at all.
The data is read randomly from all three disks (I think it's load-balanced by
process ID); if one disk happened to silently return corrupt data, that's it,
your app just got corrupt data passed to it, and if happens to write it back
to disk (maybe after some processing), then the incorrect data will be
faithfully replicated by md to all three disks. So in the future you have not
even a _chance_ to read back the correct data that was previously there.
> 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.
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. Don't forget if for example a rogue program
gets 'root' on your machine and overwrites the md device with zeroes, it will
be instantly replicated to all three disks as well.
As for me, if I lose my primary RAID6, it's a maximum a day's worth of
changes, and some data transfer from here and there to get it all copied from
backups and be up and running again. (I could reduce even that risk and easily
back up 4 times a day, but do not see the need at the moment.)
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-17 4:20 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 [this message]
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=20130417102052.20c40887@natsu \
--to=rm@romanrm.ru \
--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.