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

Scott James Remnant scott at canonical.com
Thu Apr 1 22:12:56 UTC 2010


On Thu, 2010-04-01 at 21:18 +0000, ceg wrote:

> > blkid currently, deliberately, returns only the first detected RAID or LUKS container
> > for a filesystem - with the checking order being raid first.
> 
> Did someone change it already?
> 
Not that I know of.  blkid has been refactored, but the order looks the
same to me.

> The issue I reported is actually the other way around. A RAID member
> device partition  (version 0.90 metadata, located at the end of the
> device) where the assembled raid contained LUKS was identified as being
> LUKS. Leading to a random raid member being opened and mounted instead
> of the then degraded raid device (corrupting of the raid integrity).
> 
My understanding of the code is that (with 2.17.2 anyway) this will
return RAID.

Have you tried this with current lucid?

Scott
-- 
Scott James Remnant
scott at ubuntu.com

-- 
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 Kernel
Bugs, which is subscribed to util-linux in ubuntu.




More information about the kernel-bugs mailing list