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.
Description of problem:
I'm not sure if this only LVM fault. Here is my setup:
Dell PE r815 with three controllers:
H200, H700 and HBA 6Gb which connects to an external chassis and here is where a VG becomes lost, only this one VG.
There are six VGs in the system in total, some of them comprise multiple devices, some just single device.
VG which becomes lost spans multiple disks but only from that one external chassis. Every reboot renders: PVs .. cannot be found (or similar).
It suffice to:
$ vgscan --cache
and:
$ vgchange -ay lsi0
and VG comes back to normal... until next reboot.
Version-Release number of selected component (if applicable):
lvm2-2.02.130-5.el7_2.5.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
WARNING: Device for PV QFVVeZ-d1bh-zfGs-xkFE-ZZnz-T0c3-vqZ2DF not found or rejected by a filter.
just updated the OS: lvm2-2.02.166-1.el7.x86_64 + 3.10.0-514.el7.x86_64 = problem persists
Hi
Could you please attach 'pvs -vvvv' output when your VG is NOT visible ?
Also 'lsblk' and whole boot log (ideally take lvmdump output)
(eventually sosreport if RHEL user).
My best guest is - you use 'lvmetad' and it's not informed about appearance of disk (your missing PV) in your system.
If your PV sits on some 'special' disk type - it's quite well possible that udev rules are not handling well all events.
updates via yum and two reboots and system boots fine.
But I am not saying lvm updates were the fix here, I've seen the system booted fine before the updates, one or twice, I don't know if it is random or there is a pattern to it.
I'll try to reboot once a week and as soon as the problem occurs I'll get the info requested.
One thing is certain, no special disks, it's Dell HBA to a Supermicro chassis with tradition PMR disks, Hitachi HDS723030ALA640 and Seagate ST6000NM0024-1HT17Z.
Closing this bug as requested trace is mandatory for getting any insight into this problem. We can't reproduce it without it.
In case you can provide trace - please feel free to reopen.