Comment 23 for bug 531240
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote Re: breaking raid: root raid_member opened as luks | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
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?