linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Roman Mamedov <rm@romanrm.net>
Cc: Brad Campbell <lists2009@fnarfbargle.com>, Bart Kus <me@bartk.us>,
	linux-raid@vger.kernel.org
Subject: Re: md-raid paranoia mode?
Date: Thu, 12 Jun 2014 16:45:07 +1000	[thread overview]
Message-ID: <20140612164507.3af9fe1d@notabene.brown> (raw)
In-Reply-To: <20140612122814.2db74377@natsu>

[-- Attachment #1: Type: text/plain, Size: 2708 bytes --]

On Thu, 12 Jun 2014 12:28:14 +0600 Roman Mamedov <rm@romanrm.net> wrote:

> On Thu, 12 Jun 2014 10:15:32 +0800
> Brad Campbell <lists2009@fnarfbargle.com> wrote:
> 
> > On 11/06/14 14:48, Bart Kus wrote:
> > > Hello,
> > >
> > > As far as I understand, md-raid relies on the underlying devices to
> > > inform it of IO errors before it'll seek redundant/parity data to
> > > fulfill the read request.  I have, however, seen certain hard drives
> > > report successful reads while returning garbage data.
> > 
> > If you have drives that return garbage as valid data then you have far 
> > greater problems than what you are suggesting will fix. So much so I 
> > suggest you document these instances and start banging a drum announcing 
> > them in a name and shame campaign. That sort of behavior from storage 
> > devices is never ok, and the manufacturer needs to know that.
> 
> If your RAM can return garbage, that's not a justification for having ECC RAM.
> ECC RAM is a gimmick invented by weak conformist people. Instead, you should go
> and loudly scream at the manufacturer who sold you that RAM! Errors from RAM
> are never OK! RAM should always work perfectly! And if it doesn't, you have
> greater problems. We shall not tolerate this behavior! So go get a drum and
> start banging it as loudly as you can! Name and shame the manufacturer who
> sold you that RAM. Fight the power, brother!!!

Your screwdriver is leaking  (*).

Hard drives contain ECC.  It should ensure undetected errors are an
*extremely* rare event (more rare than bugs in the md code).

If your ECC RAM started returning bad data without telling you, would you
build a complex virtual memory system to load every byte from two different
DIMMs into CPU registers and compare them before trusting them?

I know that hard drives can return bad data.  I've seen it happen.  I don't
think that trying to "fix" it in the md/raid layer is appropriate.

File-systems and higher level data management systems (e.g. git) are much
better placed to detect such errors than md/raid is.  Supposedly btrfs will
DTRT with your drives (though TRT is to RMA them, and I don't think btrfs
has an RMA plugin yet).

> 
> You can probably tell just how sick I am of reasoning like yours. That's why
> we can't have nice things (md-side resiliency for the cases when you need/want
> it), and sadly Neil is of the same opinion as you.
> 

In general, if you want nice things you need to pay for them.  If you are
willing to pay I suspect you can find someone who is willing to provide.

NeilBrown

(*)http://www.zazzle.com/a_bad_analogy_is_like_a_leaky_screwdriver_tshirts-235102919981826183

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-06-12  6:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  6:48 md-raid paranoia mode? Bart Kus
     [not found] ` <CAH3kUhH06kpJNqb-zdcv5nu2e1FeZuotcW0SjBbWDOCcasm9OA@mail.gmail.com>
2014-06-11 10:34   ` Bart Kus
2014-06-12  7:26     ` Mattias Wadenstein
2014-06-11 17:31 ` Piergiorgio Sartor
2014-06-12  2:15 ` Brad Campbell
2014-06-12  6:28   ` Roman Mamedov
2014-06-12  6:45     ` NeilBrown [this message]
2014-06-12  7:26     ` David Brown
2014-06-12  8:06       ` Roman Mamedov
2014-06-12  8:30         ` Brad Campbell
2014-06-12  8:53         ` Roman Mamedov
2014-06-12 11:27         ` David Brown

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=20140612164507.3af9fe1d@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=me@bartk.us \
    --cc=rm@romanrm.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).