From: NeilBrown <neilb@suse.de>
To: Jean-Baptiste Thomas <cau2jeaf1honoq@laposte.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Paranoid mode for RAID-1 ?
Date: Mon, 27 Apr 2015 16:49:24 +1000 [thread overview]
Message-ID: <20150427164924.2aee3831@notabene.brown> (raw)
In-Reply-To: <972437107.22507366.1430116679975.JavaMail.zimbra@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
On Mon, 27 Apr 2015 08:37:59 +0200 (CEST) Jean-Baptiste Thomas
<cau2jeaf1honoq@laposte.net> wrote:
> I'm looking for a way to get MD to operate in a mode in which
> reading a sector from a RAID-1 device would not succeed until it
> got matching data from at least two components.
>
> Recent experience[1] suggests that a transient problem in one
> disk can completely hose a four way RAID-1 array, which is
> otherwise supposed to still be fine after a triple total
> failure. I'm hoping that a paranoid mode would have prevented
> that.
>
> If there is such a thing, PLEASE tell me. If not, please tell me
> so I don't waste any more time looking for it.
No, there is no such thing.
There "should" be no circumstance which would make it worth while.
A drive may well report an error, but it should *never* report incorrect data
as though it were correct. That is horribly broken.
The cost of running in a "safe" mode would be high, and the likely benefit
extremely low. So it is unlikely that anyone would use it for long. So
implementing it seems rather pointless.
That said: if someone were to provide an implementation I would certainly
consider reviewing it and adding it to md.
NeilBrown
>
> [1] "Massive RAID-1 desync"
> http://www.spinics.net/lists/raid/msg48681.html
> http://marc.info/?l=linux-raid&m=143003812706563&w=2
> --
> 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-04-27 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1610581828.22506051.1430116628556.JavaMail.zimbra@laposte.net>
2015-04-27 6:37 ` Paranoid mode for RAID-1 ? Jean-Baptiste Thomas
2015-04-27 6:48 ` Adam Goryachev
2015-04-27 7:15 ` David Brown
2015-04-27 7:35 ` Mikael Abrahamsson
2015-04-27 8:18 ` Adam Goryachev
2015-04-27 8:34 ` Paranoid mode for RAID-1 ? MD-RAID checksums Pasi Kärkkäinen
2015-04-27 9:15 ` Paranoid mode for RAID-1 ? Roman Mamedov
2015-04-27 6:49 ` NeilBrown [this message]
2015-04-27 10:52 ` Jean-Baptiste Thomas
2015-04-27 16:15 ` Wols Lists
2015-04-27 8:45 ` Pieter De Wit
2015-04-27 10:18 ` <DKIM> " Jean-Baptiste Thomas
2015-04-27 10:54 ` David Brown
2015-04-27 12:36 ` Jean-Baptiste Thomas
2015-04-27 13:46 ` 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=20150427164924.2aee3831@notabene.brown \
--to=neilb@suse.de \
--cc=cau2jeaf1honoq@laposte.net \
--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.