I think I understand the issue, but don't see a documented explanation of why this needs to be added to stable Ubuntu releases.
What is the actual impact to users in not having mdadm able to pass through this "broken" state information, please, and how would adding this feature to stable releases resolve this impact? My two concerns are: 1) It looks like a medium complexity patch to mdadm and that risks introducing a regression. A regression in mdadm could be very severe, such as one that results in data loss. 2) As you mention, userspace tooling might break in unexpected ways. Is mdadm intended to behave *exactly* the same after this patch is applied for users with no arrays in the new "broken" state (excluding help/usage messages etc)? In other words, is any tooling breakage limited to when an array breaks? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847924 Title: Introduce broken state parsing to mdadm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1847924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
