Alasdair G. Kergon wrote: > Surely that's it working as designed? > dmsetup tells you about mapped devices available in the running kernel. > I don't think so. "dmsetup deps" indicates the devices that your mapped device depends on. If a PV is part of a VG, that VG can't start up until that PV is present. So any LV on that VG is dependent on the PV, even if the LV doesn't have any extents on the PV. Phew.
But "dmsetup deps" doesn't reflect this - it only shows the PVs that your LV is extended onto. So if "dmsetup deps" is intended to show all the devices required to access your device, then "dmsetup deps" is wrong. However, if it's meant to only show the PVs the LV is actually residing on, then the initramfs-toos package is wrong to use this tool to determine what drivers need to go into the initramfs. To me it seems that dmsetup is in the wrong. Tony -- "dmsetup deps" does not accurately report LVM dependencies, can cause boot failure https://bugs.launchpad.net/bugs/282189 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
