Bug 744532
Summary: | udev lvm setup/link issues | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | udo <udovdh> | ||||||||||
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | medium | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | 15 | CC: | agk, bmarzins, bmr, dwysocha, harald, heinzm, jonathan, kay, lvm-team, mbroz, msnitzer, prajnoha, prockai, zkabelac | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Linux | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2011-11-03 12:44:19 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
udo
2011-10-09 09:24:00 UTC
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. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. 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
|