[Bug 531240] Re: silently breaking raid: root raid_members opened as luks

[ceg]

Thank you for helping to track this down.

So the superblock on the member that got mis-opened appears to have been
overwritten. Maybe by writing/using to the opened luks device that
thought the full partition is used by luks, without respecting the room
of the raid superblock at the end of the disk.


How can opening a member happen? The cryptsetup-hook tries to identify the luks dependencies of ther rootfs.
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/cryptsetup/lucid/annotate/head%3A/debian/initramfs/cryptroot-hook

May be cryptsetup selects a raid member as source device, or the right
luks UUID is identified but gets tested againsts the raid member and it
incorrectly matches ("cryptsetup isLuks" does not recongnize it really
is a raid member not a luks device).

-- 
silently breaking raid: root raid_members opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.