Lets think some more of signature rules. Crypt vs Container -> any crypt should be lower then other containers (not fs) because whaterver is in it wouldn't be visible or is random.
Crypt vs FS <- old fs signatuers may have remained. RAID vs LVM-LV <- LVs never reside on RAIDs directly (always on PVs) <- RAID should never contain a LV directly, so its a new raid member RAID vs LVM-PV <- RAID can not be made assembled from PVs only from LVs. <- RAID can contain a PV. (only implement rules as far as understandable, never a generalization without a general rule) Upstream seems to generally refrain from prioritizing. There is of course the basic rule to return -1 (no type) if there are conficts, and no resolving rule applies. -- 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
