From: Thiemo Nagel <thiemo.nagel@ph.tum.de>
To: Mattias Wadenstein <maswan@acc.umu.se>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: On the subject of RAID-6 corruption recovery
Date: Mon, 07 Jan 2008 12:10:31 +0100 [thread overview]
Message-ID: <478208A7.2000108@ph.tum.de> (raw)
In-Reply-To: <Pine.GSO.4.64.0801071055200.20667@montezuma.acc.umu.se>
Mattias Wadenstein wrote:
> On Mon, 7 Jan 2008, Thiemo Nagel wrote:
>
>>> What you call "pathologic" cases when it comes to real-world data are
>>> very common. It is not at all unusual to find sectors filled with
>>> only a constant (usually zero, but not always), in which case your
>>> **512 becomes **1.
>>
>> Of course it would be easy to check how many of the 512 Bytes are
>> really different on a case-by-case basis and correct the exponent
>> accordingly, and only perform the recovery when the corrected
>> probability of introducing an error is sufficiently low.
>
> What is the alternative to recovery, really? Just erroring out and
> letting the admin deal with it, blindly assume that the parity is wrong?
Currently, 'repair' does blind recalculation of parity. The only
benefit of that is (correct me if I'm wrong) to ascertain repeated reads
return identical data.
The last time I checked, there was not even a warning message.
Kind regards,
Thiemo Nagel
next prev parent reply other threads:[~2008-01-07 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 2:58 On the subject of RAID-6 corruption recovery H. Peter Anvin
2007-12-28 14:38 ` Bill Davidsen
2007-12-28 17:34 ` H. Peter Anvin
2008-01-04 23:59 ` Thiemo Nagel
2008-01-05 0:03 ` H. Peter Anvin
2008-01-05 0:41 ` Thiemo Nagel
2008-01-05 0:45 ` H. Peter Anvin
2008-01-05 1:25 ` Thiemo Nagel
2008-01-05 1:49 ` H. Peter Anvin
2008-01-07 9:28 ` Thiemo Nagel
2008-01-07 9:58 ` Mattias Wadenstein
2008-01-07 11:10 ` Thiemo Nagel [this message]
2008-01-07 17:20 ` H. Peter Anvin
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=478208A7.2000108@ph.tum.de \
--to=thiemo.nagel@ph.tum.de \
--cc=hpa@zytor.com \
--cc=linux-raid@vger.kernel.org \
--cc=maswan@acc.umu.se \
/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).