Bug#311057: Bug 311057
hi all, the bug is even worth, cause lvm2 uses then only the realdisk (dev/sda3) instead the raid-disk (/dev/md2). so if you figure out the problem and move the startup-scripts for lvm after the first boot YOUR DATA ARE GONE!!! cause the system does not recognize the raid-array as inconsistent and use it as consistent array! your data are also gone, if you try to startup your old kernel 2.4.x that's really bad thomas -- # Thomas Stegbauer # http://www.keyserver.de:11371/pks/lookup?op=getsearch=0x275931BF # Key fingerprint = 984E D4B1 E91E F349 5057 B6AC 65CE C0FC 2759 31BF signature.asc Description: OpenPGP digital signature
Bug#311057: Bug 311057
Yes, lvm1 used 25 and a fresh lvm2 install uses 26, but switching from lvm1 to lvm2 leaves the start script at 25. This causes a severe bug for those running lvm on raid, since mdadm also starts at 25, but after the old lvm25 (by alphabetical ordering). For example, on my system I run three raid one components: md0 (which becomes /boot), md1 (which becomes /) and md2 which becomes an lvm. But, because lvm gets ahead of mdadm, the md2 raid device does not get started properly, only using one of the disks, with the other one somehow rendered inoperable. --Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
