It may or may not have been /intentional/, but it's clearly a /bug/ to convert /dev/mapper entries to UUID; and as soon as we can identify the code responsible for such migration (which we haven't yet), that should be fixed.
> When I change all LVM entries to /dev/mapper other bugs get in the > way of testing. I just did that and also removed all snapshots. What > happens then is that /opt can't be mounted (/dev/mapper/vg0-opt) If you convert all your fstab entries to /dev/mapper *except* for the vg0-opt entry that's currently giving you problems, and you create snapshots, does the boot work as expected? > Ownership permissions of /dev/mapper/vg0-opt are root:disk I don't see anything wrong with that; this is the default group ownership set by udev for block devices, and I have entries under /dev/mapper here that are owner root:disk. (I also have other devices that are owner root:root; the difference appears to be whether the devices were activated in the initramfs or in the root system. The devmapper device here that's owned by root:disk is an encrypted test partition that is only decrypted after chrooting to the rootfs.) Do you know of any reason why vg0-opt would be activated after the end of your initramfs instead of at the same time ? Can you attach a /var/log/udev.log for this system? -- When snapshots exists, mountall will not mount the parent partition https://bugs.launchpad.net/bugs/563902 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
