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 21:27:52 -0700 [thread overview]
Message-ID: <516E24C8.9080803@tigertech.com> (raw)
In-Reply-To: <516DFC4F.5000908@websitemanagers.com.au>
On 4/16/13 6:35 PM, Adam Goryachev wrote:
> Obviously, if they suffered a two disk [RAID 1] failure then they won't
> be here asking for help will they :)
Heh. Well, no, they won't if the disks are completely and permanently dead.
(I know I'm starting to sound like a broken record, but "that's partly
why we use three disks instead of two and make sure they don't all use
the same company's firmware".)
But complete disk death doesn't seem to be the normal failure mode.
If the failure is spurious, as so many seem to be, and temporarily
affects an array so that each disk has a different event count, that
isn't a disaster under RAID 1. If worst comes to worst, you can pick one
disk to use and pretend RAID doesn't even exist. You don't need to get
the members to successfully sync into an array to read the data.
But if each disk in a RAID 5 or RAID 6 array gets a different event
count, or if the disks refuse to easily assemble into an active array
for any other reason, all your data is inaccessible until you fix the
RAID problem.
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.
--
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
next prev parent reply other threads:[~2013-04-17 4:27 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 [this message]
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=516E24C8.9080803@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.