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 1388962 - Prevent activation of RAID4 with kernels not supporting proper mapping
Summary: Prevent activation of RAID4 with kernels not supporting proper mapping
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Heinz Mauelshagen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1385149 1386184 1386194
Blocks: 1395563
TreeView+ depends on / blocked
 
Reported: 2016-10-26 15:00 UTC by Heinz Mauelshagen
Modified: 2021-09-03 12:52 UTC (History)
13 users (show)

Fixed In Version: lvm2-2.02.169-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1386184
: 1395563 (view as bug list)
Environment:
Last Closed: 2017-08-01 21:49:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2222 0 normal SHIPPED_LIVE lvm2 bug fix and enhancement update 2017-08-01 18:42:41 UTC

Comment 1 Heinz Mauelshagen 2016-10-26 15:04:39 UTC
This bz is coping with rejecting raid4 activation and conversion to/from on dm-raid target 1.[89].0 which does not provide correct raid4 mapping.

Comment 2 Heinz Mauelshagen 2016-10-27 09:43:03 UTC
Upstream commit ff05ed7afd16

Comment 3 Heinz Mauelshagen 2016-11-15 18:03:04 UTC
Corey,

test with creating a raid4 LV with raid target versions 1.[89].0 (e.g. kernel-3.10.0-515.el7) or converting to raid4 which gets rejected with
"RAID module does not support RAID4.".

Comment 7 Corey Marthaler 2016-11-17 23:56:34 UTC
Filed bug 1396309 for the raid10 version of this issue that was originally mentioned in bug 1385149.

Comment 9 Roman Bednář 2017-05-16 08:47:24 UTC
Marking verified. Raid 4 volume activation is prevented when using
incompatible versions of raid dm target and lvm2.

=============================================

Initial packages (RHEL7.2):
	3.10.0-327.el7.x86_64
	lvm2-2.02.130-5.el7.x86_64

# dmsetup targets|grep raid
raid             v1.7.0


# lvs -a -o lv_name,segtype,devices -S vg_name=vg
  LV               Type   Devices                                                                
  raid4            raid4  raid4_rimage_0(0),raid4_rimage_1(0),raid4_rimage_2(0),raid4_rimage_3(0)
  [raid4_rimage_0] linear /dev/sda(1)                                                            
  [raid4_rimage_1] linear /dev/sdb(1)                                                            
  [raid4_rimage_2] linear /dev/sdc(1)                                                            
  [raid4_rimage_3] linear /dev/sdd(1)                                                            
  [raid4_rmeta_0]  linear /dev/sda(0)                                                            
  [raid4_rmeta_1]  linear /dev/sdb(0)                                                            
  [raid4_rmeta_2]  linear /dev/sdc(0)                                                            
  [raid4_rmeta_3]  linear /dev/sdd(0)      

# vgchange -an vg

BEFORE PATCH:
Upgrade to 3.10.0-514.el7 and lvm2-2.02.166-1.el7

# dmsetup targets|grep raid
raid             v1.9.0

# pvscan --cache

# pvscan
  PV /dev/sdi    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdg    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdf    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sda    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdh    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdc    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdb    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdd    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sde    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdj    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/vda2   VG rhel_virt-369   lvm2 [7.51 GiB / 40.00 MiB free]
  Total: 11 [407.43 GiB] / in use: 11 [407.43 GiB] / in no VG: 0 [0   ]

# lvchange -ay vg/raid4
  device-mapper: reload ioctl on (253:22) failed: Invalid argument


May 16 10:31:10 virt-369 kernel: device-mapper: raid: Reshaping/takeover raid sets not yet supported. (raid level/stripes/size change)
May 16 10:31:10 virt-369 kernel: device-mapper: table: 253:22: raid: Unable to assemble array: Invalid superblocks
May 16 10:31:10 virt-369 kernel: device-mapper: ioctl: error adding target to table
May 16 10:31:10 virt-369 multipathd: dm-22: remove map (uevent)
May 16 10:31:10 virt-369 multipathd: dm-22: remove map (uevent)


AFTER PATCH:
Upgrade to lvm2-2.02.171-1.el7.x86_64

# dmsetup targets|grep raid
raid             v1.9.0

# uname -r
3.10.0-514.el7.x86_64

# pvscan --cache

# pvscan
  PV /dev/sdi    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdg    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdf    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sda    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdh    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdc    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdb    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdd    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sde    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/sdj    VG vg              lvm2 [39.99 GiB / 39.88 GiB free]
  PV /dev/vda2   VG rhel_virt-369   lvm2 [7.51 GiB / 40.00 MiB free]
  Total: 11 [407.43 GiB] / in use: 11 [407.43 GiB] / in no VG: 0 [0   ]

# lvchange -ay vg/raid4
  RAID module does not support RAID4.
  Failed to activate raid4 LV vg/raid4

=============================================

Comment 10 errata-xmlrpc 2017-08-01 21:49:49 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://access.redhat.com/errata/RHBA-2017:2222


Note You need to log in before you can comment on or make changes to this bug.