Public bug reported:
i`m using gutsy tribe5 with root fs on lvm2 volume (/dev/mapper/sunset-root) .
when i`m creating snapshot of root device (/dev/mapper/sunset-root--19--09) lvm
creats three (!) devices
with same UUID:
before creating:
/dev/mapper/sunset-root (block 254,0) aka /dev/dm-0
after:
/dev/mapper/sunset-root-real (block 254,0) aka /dev/dm-0 (oops!)
/dev/mapper/sunset-root (block 254,1) aka /dev/dm-1 (new data, after creating)
/dev/mapper/sunset-root--19--09 (block 254,3) aka /dev/dm-3 (old data, before
creating)
all with same UUID, but it is only the first liltle problem. another problem is
that fisrt device (dm-0) can`t be mounted, but udev
creates symlink in /dev/disk/by-uuid to it (on initramfs boot stage), so system
can`t boot
other big problem for me is that update-grub rewrites my
kopt=root=/dev/dm-1 rot UUID form
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Affects: grub (Baltix)
Importance: Undecided
Status: New
** Also affects: grub (Baltix)
Importance: Undecided
Status: New
--
creating lvm2 snapshot of root lv breaks boot
https://bugs.launchpad.net/bugs/144049
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
