linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Michael Ole Olsen <gnu@gmx.net>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm raid5 and bit errors resync
Date: Wed, 24 Jun 2009 13:23:39 +1000	[thread overview]
Message-ID: <19009.39995.508538.297396@notabene.brown> (raw)
In-Reply-To: message from Michael Ole Olsen on Monday June 22

On Monday June 22, gnu@gmx.net wrote:
> what happens in the case of a single unrecoverable bit error when resyncing a
> raid5 or upgrading it?

During resync, a read error will cause the drive to fail and the
resync to abort.  So you get a degraded array.  On the next restart,
you will need to --force assemble the array because it will appear not
to be 'clean'.

What exactly do you mean by "uprade".

> 
> and in the case of raid6?

The same.

> 
> would raid6 only be able to survive 2 bit errors?

I don't understand why you are focussing on 'bit' error.  raid deals
with whole blocks, which either succeed or fail.
During resync you cannot trust the parity, so any read error means
lost data.
During recovery (to a hot spare) for a partially degraded raid6, the
correct data will be generated from the remaining good drives and
written out.

NeilBrown


> 
> couldn't really find any information on it in the docs or google, but I have
> heard about systems failing because of single bit errors.
> 
> /Michael Ole Olsen

      reply	other threads:[~2009-06-24  3:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22  5:58 mdadm raid5 and bit errors resync Michael Ole Olsen
2009-06-24  3:23 ` Neil Brown [this message]

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=19009.39995.508538.297396@notabene.brown \
    --to=neilb@suse.de \
    --cc=gnu@gmx.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 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).