From: Robert Buchholz <robert.buchholz@goodpoint.de>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Find mismatch in data blocks during raid6 repair
Date: Thu, 21 Jun 2012 16:58:33 +0200 [thread overview]
Message-ID: <5100581.utCIcpy8f5@peanut> (raw)
In-Reply-To: <4FE315CE.9090201@anonymous.org.uk>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Hello John,
On Thursday, June 21, 2012 01:38:38 PM John Robinson wrote:
> On 20/06/2012 18:41, Robert Buchholz wrote:
> [...]
>
> > When repairing a full raid6 with no missing drives
> > (raid-devices=n+2), a single inconsistent data block could be
> > detected
>
> Yes, it could. See Neil Brown's blog post as to the many reasons why
> this isn't implemented: http://neil.brown.name/blog/20100211050355
Thank you for the pointer, I did not find the article before.
I agree with Neil's premise, this should not be run on a mounted raid as
changing data blocks can be a problem, and it should not be the default
for resync. However, as both Neil and commenters point out, this is a
valuable (offline) repair option.
Do you know whether the "smart" algorithm or the API necessary to
construct a user space program are on the agenda?
Cheers
Robert
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-21 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 17:41 Find mismatch in data blocks during raid6 repair Robert Buchholz
2012-06-21 12:38 ` John Robinson
2012-06-21 14:58 ` Robert Buchholz [this message]
2012-06-21 18:23 ` Piergiorgio Sartor
2012-06-29 18:16 ` Robert Buchholz
2012-06-30 11:48 ` Piergiorgio Sartor
2012-07-03 19:10 ` Robert Buchholz
2012-07-03 20:27 ` Piergiorgio Sartor
2012-07-09 3:43 ` NeilBrown
2012-07-20 10:40 ` [PATCH] " Robert Buchholz
2012-07-20 14:14 ` Robert Buchholz
2012-07-20 10:53 ` Robert Buchholz
2012-07-21 16:00 ` Piergiorgio Sartor
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=5100581.utCIcpy8f5@peanut \
--to=robert.buchholz@goodpoint.de \
--cc=john.robinson@anonymous.org.uk \
--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.