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.
Bug 1207714 - dm-cache doesn't work with kernel 3.10.0-229.1.2.el7.x86_64
Summary: dm-cache doesn't work with kernel 3.10.0-229.1.2.el7.x86_64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-31 14:27 UTC by Marko Karg
Modified: 2023-03-08 07:27 UTC (History)
14 users (show)

Fixed In Version: lvm2-2.02.124-1.el7
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2015-11-19 12:46:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Configuration for vg_data (5.61 KB, text/plain)
2015-03-31 14:27 UTC, Marko Karg 		no flags Details
rdsosreport file (123.11 KB, text/plain)
2015-03-31 14:28 UTC, Marko Karg 		no flags Details
patch (1.04 KB, patch)
2015-04-01 08:49 UTC, Marko Karg 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1427223 0 None None None Never
Red Hat Product Errata RHBA-2015:2147 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2015-11-19 11:11:07 UTC

Description Marko Karg 2015-03-31 14:27:22 UTC 
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.
Comment 1 Marko Karg 2015-03-31 14:28:16 UTC 
Created attachment 1009091 [details]
rdsosreport file
Comment 3 Jose Castillo 2015-03-31 14:55:41 UTC 
Marko, I think this looks similar to bz #1187080 fixed with the following patch:
 https://www.redhat.com/archives/lvm-devel/2015-January/msg00073.html

In fedora 21. Maybe you can try backporting to RHEL 7 it and see if it helps?
Comment 4 Marko Karg 2015-04-01 08:48:29 UTC 
The attached patch solved the issue for me, thanks Jose!
Comment 5 Marko Karg 2015-04-01 08:49:29 UTC 
Created attachment 1009546 [details]
patch
Comment 6 Zdenek Kabelac 2015-08-24 08:57:02 UTC 
The bug is already fixed upstream.
Comment 8 Corey Marthaler 2015-09-11 20:22:47 UTC 
Marking verified with the current rpms. No internal errors while running basic cache regression tests.


3.10.0-313.el7.x86_64
lvm2-2.02.130-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
lvm2-libs-2.02.130-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
lvm2-cluster-2.02.130-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
device-mapper-1.02.107-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
device-mapper-libs-1.02.107-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
device-mapper-event-1.02.107-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
device-mapper-event-libs-1.02.107-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
device-mapper-persistent-data-0.5.5-1.el7    BUILT: Thu Aug 13 09:58:10 CDT 2015
cmirror-2.02.130-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
sanlock-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
sanlock-lib-3.2.4-1.el7    BUILT: Fri Jun 19 12:48:49 CDT 2015
lvm2-lockd-2.02.130-1.el7    BUILT: Wed Sep  9 02:44:18 CDT 2015
Comment 9 errata-xmlrpc 2015-11-19 12:46:15 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.