My understanding of this problem:
blkid currently, deliberately, returns only the first detected RAID or
LUKS container for a filesystem - with the checking order being raid
first.
This means if a partition has both a RAID and LUKS signature, it will
always be returned as RAID.
You request that we invert this, so that a partition that has both a
RAID and LUKS signature is now returned as LUKS.
My concern here is that in the case where we added LUKS to that break-
out rule, we were only changing a "no answer" result to one with a
probably valid (or at least not dangerously invalid) answer.
The change you're asking for is *changing* an existing answer.
Why is it impossible that there are systems out there whose RAID devices
have left-over LUKS metadata on them?
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: util-linux (Ubuntu)
Status: Triaged => Incomplete
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
