No, you're looking at it backwards. cryptsetup should not have to carry any embedded information about what identifies a RAID container, that's the responsibility of blkid. The bug is that the cryptsetup job is *being called at all* for this block device.
-- 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
