All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Goryachev <mailinglists@websitemanagers.com.au>
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 14:45:14 +1000	[thread overview]
Message-ID: <516E28DA.7070102@websitemanagers.com.au> (raw)
In-Reply-To: <516E24C8.9080803@tigertech.com>

On 17/04/13 14:27, Robert L Mathews wrote:
> 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. 
RAID1 of course fails the requirement of a single filesystem that
requires more space than a single disk can provide.

Of course, you can then consider LVM2, multiple mount points, or RAID10
or RAID1 + linear etc.... but most people still prefer to see a single
block device. Dealing with multiple RAID1 and a linear could lead to
more complex issues as well.

In any case, as mentioned previously, the majority of issues are caused
by mis-configuration, if we could add some configuration verification to
mdadm or similar, then we might be able to warn more people prior to
things failing.

Regards,
Adam

-- 
Adam Goryachev
Website Managers
www.websitemanagers.com.au


  reply	other threads:[~2013-04-17  4:45 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 [this message]
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=516E28DA.7070102@websitemanagers.com.au \
    --to=mailinglists@websitemanagers.com.au \
    --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.