Package: mdadm
Version: 3.0.3-2
Severity: normal
Following up to my initial report in this bug, I finally found
that not messing with the metadata line generated correctly by mkconf
but rather removing the name portion of the line fixed the problem for
my mdadm entry that is using metadata=1.2.
Hopefully that will help someone else who might run into this
problem.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
