Summary: | sys-fs/lvm2-2.02.42: init.d/lvm should have 'need device-mapper' line | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Kazantsev <mk.fraggod> |
Component: | New packages | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | agk, cardoe |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Kazantsev
2009-01-17 05:25:52 UTC
Oh, forgot to mention that /dev/sda4-based vg 'aux' also contains /dev/aux/root lv (xfs), which is successfully mapped and mounted by initrd. Thanks for reporting this issue (and your solution). Assigning to maintainers. LVM itself depends on the device-mapper module. It does NOT depend on the device-mapper init script. The device-mapper init script really should be called dmtab, because it creates all of the volumes defined in /etc/dmtab (After loading the device-mapper module if needed). The LVM script loads the device-mapper module, and followed by pvscan, vgscan, vgchange. "need device-mapper" is not correct. "after device-mapper" is. However, you can still create systems that are foiled by that route. Use DM-RAID on your disks, with LVM in the middle, and another DM layer on top of that. I added "after device-mapper" for now. |