mdadm raid5 and bit errors resync

mdadm raid5 and bit errors resync

[Michael Ole Olsen]

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

what happens in the case of a single unrecoverable bit error when resyncing a
raid5 or upgrading it?

and in the case of raid6?

would raid6 only be able to survive 2 bit errors?

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

Re: mdadm raid5 and bit errors resync

[Neil Brown]

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