Description of problem: dracut mentions that /dev/mapper nodes for lvm2 devices was not set up by udev; also dracut mentions that links under /dev were not created by udev Version-Release number of selected component (if applicable): udev-167-6.fc15.x86_64 How reproducible: get kernel from kernel.org compile kernel install kernel boot into kernel Steps to Reproduce: 1. see above 2. 3. Actual results: see below Expected results: no such dracut complaints about udev Additional info: dracut: Scanning devices dm-0 for LVM volume groups dracut: Reading all physical volumes. This may take a while... dracut: Found volume group "myvg" using metadata type lvm2 dracut: /dev/mapper/myvg-usrlv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-varlv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-homelv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-datalv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-srclv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-optlv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-wwwlv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-newrootlv not set up by udev: Falling back to direct node creation. dracut: /dev/mapper/myvg-rootlv not set up by udev: Falling back to direct node creation. dracut: The link /dev/myvg/usrlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/varlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/homelv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/datalv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/srclv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/optlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/wwwlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/newrootlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: The link /dev/myvg/rootlv should had been created by udev but it was not found. Falling back to direct link creation. dracut: 9 logical volume(s) in volume group "myvg" now active What is wrong? User error? kernel missing the fedora magic? Please let us know what info I can provide to help you fix or explain this issue. Thanks.
Do you really want me to debug your kernel .config ? You probably have forgotten some udev cookie settings for lvm.
You mean there's now howto for such stuff? When I google "udev cookie settings for lvm" I get stuff like http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/udev_commands_interfaces.html which implies that I'd have to dig into udev scripting voodoo which I assume to be provided by Redhat/Fedora. If just the kernel is custom, the initrd scripting is not. (!?) Is some of the magic in this bug described at https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/802626 ? There is no howto for such stuff? Which kernel .config section is related to this udev/lvm issue so I can have look myself?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
For interested readers: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=690308 (learned me a tad about what is going on)
(In reply to comment #0) > dracut: Found volume group "myvg" using metadata type lvm2 > dracut: /dev/mapper/myvg-usrlv not set up by udev: Falling back to direct node > creation. ... > What is wrong? User error? kernel missing the fedora magic? > Please let us know what info I can provide to help you fix or explain this > issue. Can you reproduce this if you deactivate/activate an LV later after the boot is complete? E.g. try to deactivate a volume that is not in use right after boot temporarily (I guess the "datalv" could be used for this test) and try to grab the debug output with -vvvv: "lvchange -an -vvvv myvg/datalv" and attach it here, please. Thanks.
Created attachment 531381 [details] log as requested
Hmm, data was still in use, will retry.
Created attachment 531385 [details] log as requested
Created attachment 531386 [details] log of activation
Well, looking at the logs, this is another instance of the problem that is already reported as bug #727925: #ioctl/libdm-iface.c:2017 Uevent not generated! Calling udev_complete internally to avoid process lock-up. We found out one source of this problem, see also bug #727925 comment #4 and comment #11. Unfortunately, it seems we haven't found all possible sources of this problem based on the comment bug #727925 comment #12. I'll close this bug as duplicate and add you on CC in the other bug report. Stay tuned... *** This bug has been marked as a duplicate of bug 727925 ***
(In reply to comment #0) > How reproducible: > get kernel from kernel.org > compile kernel Please, send the .config of the self-compiled kernel so we can compare it with the one in bug #727925 to see if there's something in common that might cause this bug to happen. Thanks.
Created attachment 531575 [details] kernel config