Comment # 6 on bug 1175105 from
(In reply to Ralf Czekalla from comment #5)
> Seriously guys? 
> => Misleading error messages by an important tool - we are talking about
> mdadm here, right? 
> First to-be-fixed issue! At least it should bring an appropriate error
> message and recommend the possibility to fix this problem with wipefs.

Adding an proper error message might be a practical fix which might be
acceptable by upstream maintainer. Could you please to provide a suggested
error message to avoid misunderstanding in this case ?

> => wipefs should automatically be called by mdadm here! 
> Second necessary fix: Call wipefs automatically if mdadm recognizes that it
> can not cope with the bits and bytes of dirt during md creation and run it
> on the device mdadm is supposed to use!

This is hard and complicated, to make mdadm correctly recognize the error
condition is really not easy, and erase the meta data automatically is risky
and won't have full support from all developers.

I do need your help to provide your opinion and suggestion on how to provide
the error information and a preferred message content. At least the information
which you think may make you feel better, then I can try to compose a patch.

Thanks in advance.

Coly Li

You are receiving this mail because: