Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRodrigo A B Freire
2016-08-30 20:30:33 UTC
Description of problem:
multipath-based LVM is not activated at system startup, thus causing
Version-Release number of selected component (if applicable):
device-mapper-1.02.107-5.el7_2.1.x86_64
How reproducible:
Intermitent; always in some select systems
Steps to Reproduce:
1. Present 4 1-TB LUN to the system
2. Set the volumes as a 4 TB VG / LV
3. Configure it to mount at startup in
Actual results:
System should activate the VGs upon boot time
Expected results:
VGs are not activate and boot fails because of missing LV.
Additional info:
This issue is mitigated by disabling lvmetad (lvmetad = 0 in /etc/lvm/lvm.conf)
If possible, please follow instructions to collect more debug info as already described in bug #1324028 comment #10 and attach it here.
Also, would it be possible for the customer(s) to try the latest 7.2.z lvm2/device-mapper (lvm2-2.02.130-5.el7_2.5) and device-mapper-multipath (device-mapper-multipath-0.4.9-85.el7_2.6) packages and check if they can still reproduce - we've fixed a few issues there which may be related.
I've yum updated my servers and seems like the issue I was having before is gone. The lvm version is now 7:2.02.130-5.el7_2.5 and multipath is 0.4.9-85.el7_2.6
(In reply to Shafi from comment #5)
> I've yum updated my servers and seems like the issue I was having before is
> gone. The lvm version is now 7:2.02.130-5.el7_2.5 and multipath is
> 0.4.9-85.el7_2.6
OK, those packages contain several important fixes in the area of device caching in LVM2 and also in the area of LVM2 and multipath cooperation.
I'm closing this bug report now. If you run into this issue again, please, reopen this report. Thanks.