linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Tao Guo <glorioustao@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data scribbling for raid6 is wrong?
Date: Thu, 15 Dec 2011 15:27:23 +1100	[thread overview]
Message-ID: <20111215152723.1d2bcca0@notabene.brown> (raw)
In-Reply-To: <CAAV8rnKoga_DM1qh28ZGEsJMZAKPYDZcVFfLBSH9kPNHysf7LQ@mail.gmail.com>

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

On Thu, 15 Dec 2011 11:15:42 +0800 Tao Guo <glorioustao@gmail.com> wrote:

> Hi all,
> 
> Today I checked the raid6's scribbling code, and I think there may be
> some improvements to handle bad sectors:

I think the common term is "scrubbing" rather than "scribbling".

> 
> If we have one bad sector(with corrupted data) in the data block,
> scribbling thread will find parity mismatch and will try to
> recompute&rewrite P&Q, but that will cause final data loss.
> Since we have P & Q,  actually we can try to use them and find out the
> wrong data block then fix it.
> 
> But the algorithm to find the bad data block seems not
> straightforward... Does anyone know if there is any paper discussed
> this issue before?
> 
> Update: I just found there is one talk about this in FAST08:
> http://www.usenix.org/events/fast08/tech/krioukov.html.
> But that approach will add checksums.etc. For bare-bones raid6, does
> any guru have any better ideas?

http://neil.brown.name/blog/20100211050355

NeilBrown

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

  reply	other threads:[~2011-12-15  4:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  3:15 Data scribbling for raid6 is wrong? Tao Guo
2011-12-15  4:27 ` NeilBrown [this message]
2011-12-15  5:48   ` Tao Guo
2011-12-15  9:33   ` 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=20111215152723.1d2bcca0@notabene.brown \
    --to=neilb@suse.de \
    --cc=glorioustao@gmail.com \
    --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 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).