linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Bart Kus <me@bartk.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: md-raid paranoia mode?
Date: Wed, 11 Jun 2014 19:31:20 +0200	[thread overview]
Message-ID: <20140611173120.GA2437@lazy.lzy> (raw)
In-Reply-To: <5397FBCE.3060009@bartk.us>

On Tue, Jun 10, 2014 at 11:48:46PM -0700, 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.
> 
> Is it possible to set md-raid into a paranoid mode, in which it reads all
> available data and confirms integrity?  Here's how it would work:
> 
> RAID6: read data + parity 1 + parity 2.  If 1 of the 3 mismatches, correct
> it, and write corrected data to the corrupt source.  Log the event.  If all
> 3 disagree, alert user somehow.
> RAID5: read data + parity.  If they mismatch, alert user somehow.
> RAID1: read data 1 + data 2.  If they mismatch, alert user somehow.
> 
> You can see this is mostly useful for RAID6 mode, where there is a chance at
> automated recovery.  However, it can also be used to prevent silent data
> corruption in the other modes, by making it not silent.

Hi Bart,

this was discussed some times ago, mainly for RAID6.
One compromise was "raid6check", which run in user space.

The main objection is the performance drop, that such a
reading method will have, which, of course, will require
an enable/disable switch.

I do not want to write for Neil, but I guess reasonable
patches, doing what you propose, will be accepted.

bye,

pg

> 
> --Bart
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

piergiorgio

  parent reply	other threads:[~2014-06-11 17:31 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 [this message]
2014-06-12  2:15 ` Brad Campbell
2014-06-12  6:28   ` Roman Mamedov
2014-06-12  6:45     ` NeilBrown
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=20140611173120.GA2437@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=me@bartk.us \
    /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).