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.
In an earlier version, LVM2 introduced support for write caching mode, which is stored in metadata. Consequently, metadata without caching mode were considered invalid and and the system could become unbootable. With this update, metadata without set cache mode use the default caching mode write-through. As a result, logical volumes with older metadata can be activated as expected.
Created attachment 1009090[details]
Configuration for vg_data
Description of problem:
Trying to do a pvscan for devices under dm-cache results in error messages and non-activated devices:
[root@colossus ~]# pvscan --cache -a ay
Internal error: LV vg_data/cachedisk has uknown feature flags 0.
Could not format metadata for VG vg_data.
Update of lvmetad failed. This is a serious problem.
It is strongly recommended that you restart lvmetad immediately.
Internal error: LV vg_data/cachedisk has uknown feature flags 0.
Could not format metadata for VG vg_data.
Update of lvmetad failed. This is a serious problem.
It is strongly recommended that you restart lvmetad immediately.
Internal error: LV vg_data/cachedisk has uknown feature flags 0.
Could not format metadata for VG vg_data.
Update of lvmetad failed. This is a serious problem.
It is strongly recommended that you restart lvmetad immediately.
The same problem prevents the system from booting properly, removing the appropriate rd_ entries in grub works around this.
Version-Release number of selected component (if applicable):
lvm2-libs-2.02.115-3.el7.x86_64
lvm2-2.02.115-3.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Set up PVs and LVs as shown in the attached file vg_data
2. Boot the system with kernel 3.10.0-229.1.2.el7.x86_64 (last known working kernel is 3.10.0-123.13.2.el7.x86_64)
3. Boot holds with these messages:
dracut-initqueue[308]: Warning: Could not boot
dracut-initqueue[308]: Warning: /dev/vg_data does not exist
Actual results:
Boot hangs when the kernel tries to activate the PVs and bails out to a rescue shell.
Expected results:
A bootup with all PVs, VGs and LVs activated.
Additional info:
rdsosreport is attached.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2147.html
Created attachment 1009090 [details] Configuration for vg_data Description of problem: Trying to do a pvscan for devices under dm-cache results in error messages and non-activated devices: [root@colossus ~]# pvscan --cache -a ay Internal error: LV vg_data/cachedisk has uknown feature flags 0. Could not format metadata for VG vg_data. Update of lvmetad failed. This is a serious problem. It is strongly recommended that you restart lvmetad immediately. Internal error: LV vg_data/cachedisk has uknown feature flags 0. Could not format metadata for VG vg_data. Update of lvmetad failed. This is a serious problem. It is strongly recommended that you restart lvmetad immediately. Internal error: LV vg_data/cachedisk has uknown feature flags 0. Could not format metadata for VG vg_data. Update of lvmetad failed. This is a serious problem. It is strongly recommended that you restart lvmetad immediately. The same problem prevents the system from booting properly, removing the appropriate rd_ entries in grub works around this. Version-Release number of selected component (if applicable): lvm2-libs-2.02.115-3.el7.x86_64 lvm2-2.02.115-3.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Set up PVs and LVs as shown in the attached file vg_data 2. Boot the system with kernel 3.10.0-229.1.2.el7.x86_64 (last known working kernel is 3.10.0-123.13.2.el7.x86_64) 3. Boot holds with these messages: dracut-initqueue[308]: Warning: Could not boot dracut-initqueue[308]: Warning: /dev/vg_data does not exist Actual results: Boot hangs when the kernel tries to activate the PVs and bails out to a rescue shell. Expected results: A bootup with all PVs, VGs and LVs activated. Additional info: rdsosreport is attached.