From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040809 Description of problem: Since running pvmove or creating a snapshot in the volume group holding the root filesystem may cause initrd's vgscan to fail if dm-mirror and/or dm-snapshot are needed but not present, it would be desirable for initrd to at least contain these modules. vgscan should probably be improved so as to attempt to load the modules on demand, but currently it doesn't, so we might have to explicitly load them. Since that amounts to about 33KiB of memory, we might as well go ahead and do it. If someone is bothered, it's easy enough to rmmod them afterwards. Version-Release number of selected component (if applicable): mkinitrd-4.1.9-1 How reproducible: Always Steps to Reproduce: 1.Have root on LVM 2.Create a snapshot in the same volume group and/or start pvmove 3.Reboot Actual Results: initrd will fail to bring up the volume group holding the root filesystem because the needed modules are missing. Expected Results: It shouldn't fail to reboot. Additional info:
agk -- comments?
Please consider this MUST FIX for FC3. The workaround around is simple, recovery from a non-startable system volume group is not.
All the dm modules (incl. mirror, snapshot, zero) need to be available when vgchange -ay gets run; currently the automatic loading code is inactive (see an old bugzilla entry), so the modules all need to be loaded before running vgchange -ay in case they are needed - this will get addressed within LVM2.
This seems a bit broken (and even if you had automatic loading present, then it wouldn't help as the modules wouldn't be there in the initrd at present). But, since my chances of getting that to change are roughly zero, I'll add those three to a list to be automatically pulled in. Will be in mkinitrd 4.1.14. And working on the anaconda modifications too since it'll be needed there as well.
Confirmed fixed, thanks.