On Wednesday 21 April 2010 03:15:32 Steve Langasek wrote: > That doesn't sound weird to me at all, it's exactly what I expected to > hear based on my own testing here. :)
No, it's still weird. I can only boot with a mix of UUID and /dev/mapper. For the moment, let's call that reliable. > So if /dev/mapper devices get mounted correctly in the presence of > snapshots, I think we can conclude that there's no bug in lvm2/mountall > wrt snapshots. No, they don't. Without snapshots (and with the mix of UUID and /dev/mapper) I can now boot, but I just tried this with snapshots. - With a snapshot of vg0/home, /home can not be mounted - With a snapshots of vg0/images, /srv/images can not be mounted > There seems to be a bug preventing /dev/mapper/vg0-opt > from working for you, but that's unrelated to snapshotting and seems to > be tracked as bug #557909. Yes. I must add that the ownership of the unmountable volumes 'root:disk' is when a snapshot of that volume exists. So, maybe fixing bug 557909 (or bug 561390) might also fix this one. > there's possibly a bug in some unidentified > component that wrongly changes /dev/mapper entries to UUID in /etc/fstab > on upgrade; and there's a need to document in the release notes that you > shouldn't use UUID= for lvs in /etc/fstab. Exactly. > Have I covered everything? Almost. I'm experiencing bug 563895. Same cause as this bug, different situation with mdadm. I'm only mentioning this because they might be related somehow. (Could be wrong. I reported that bug against grub.) -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
