On Tue, Feb 02 2016, Sarah Newman wrote: > On 01/27/2016 07:19 PM, NeilBrown wrote: >> On Thu, Jan 28 2016, Sarah Newman wrote: >> >>> Kernel: CentOS 6 Xen4CentOS 3.18.21-17 >>> mdadm: CentOS 6 v3.3.2 >>> >>> With the above behavior, I consider the bad blocks list to be actively harmful. If it's expected behavior in the current version, please consider >>> disabling the bad blocks list by default. >> >> You can do this yourself by putting >> >> CREATE bbl=no >> >> in /etc/mdadm.conf. That doesn't help others though. > > FYI, I tried adding that line and if it is present when trying to add to an array that currently has a bad blocks list, I get the error message > > md: sdi1 does not have a valid v1.0 superblock, not importing! > > Is this expected? No, that looks like a bug. If would be helpful to see complete "mdadm --examine" output of the device that you tried to add, and a device that is already in the array. Thanks, NeilBrown
Attachment:
signature.asc
Description: PGP signature
