Grown defects in a RAID array

[Dathan Vance Pattishall]

------=_NextPart_000_0110_01C3671D.228BB6C0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

I've notice that when grown defects (bad blocks on the disk caused by
usage over time) that my dedicated mysql server is adversely effected.

Since the action of Grown defects does not flush the table with a write
lock-that the block marked as bad will effect prior to that block
becoming a grown defect-what is another way for mysql to recover from
this situation?

I'm currently using EXT3 does this same effect happen with Reiser-Fs /
UFS / Veritas?

Maybe Jeremy Zawodny can help me with this?

------=_NextPart_000_0110_01C3671D.228BB6C0--