On Thu, 24 Nov 2011 13:19:53 +0100 Adam Kwolek <adam.kwolek@xxxxxxxxx> wrote: > When external metadata doesn't support BBM, mdadm cannot answer correctly > for BBM requests. It causes reshape process being stopped. > > Add ability for external metadata /mdadm/ to disable BBM via sysfs. > md will ignore bad blocks as it is for metadata v0.90. This should not be necessary. The intention is that a device with a bad block looks exactly like a device with a failed device. i.e. 'faulty' and 'blocked' appear in the 'state' file. If the metadata doesn't support a bad-block list, it will record that the device has failed and will unblock the device. At that point the failure is forced. If the metadata does support a bad block list it will just record the bad blocks and acknowledge them, and the unblock the device. At that point the device won't be failed, the 'faulty' state will disappear, and it will continue to be used with the known bad blocks. What exactly is going wrong that makes you think you need this patch? NeilBrown
Attachment:
signature.asc
Description: PGP signature
