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.

Bug 1354067

Summary: raid0 needs to be protected from raid operations that do not apply
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Heinz Mauelshagen <heinzm>
lvm2 sub component: Mirroring and RAID QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: unspecified CC: agk, heinzm, jbrassow, msnitzer, prajnoha, prockai, zkabelac
Version: 7.3Keywords: Reopened
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.161-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 04:22:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2016-07-08 23:01:55 UTC 
Description of problem:

[root@host-084 ~]# lvcreate  --nosync --type raid0 -i 2 -n zero -L 5M raid_sanity
  Using default stripesize 64.00 KiB.
  Rounding up size to full physical extent 8.00 MiB
  Logical volume "zero" created.

[root@host-084 ~]# lvcreate -n linear -L 5M raid_sanity
  Rounding up size to full physical extent 8.00 MiB
  Logical volume "linear" created.

[root@host-084 ~]# lvcreate -n stripe -i 2 -L 5M raid_sanity
  Using default stripesize 64.00 KiB.
  Rounding up size to full physical extent 8.00 MiB
  Logical volume "stripe" created.


[root@host-084 ~]# lvchange --syncaction repair raid_sanity/stripe
  raid_sanity/stripe must be a RAID logical volume to perform this action.
[root@host-084 ~]# lvchange --syncaction repair raid_sanity/linear
  raid_sanity/linear must be a RAID logical volume to perform this action.

[root@host-084 ~]# lvchange --syncaction check raid_sanity/zero
  device-mapper: message ioctl on LVM-I41GAeV8aoWdtFX92qXzNLTe1Cj3uWpaGpxBzy5dkJI623tV2r2yFSTgUVQ03yEe failed: Invalid argument
[root@host-084 ~]# lvchange --syncaction repair raid_sanity/zero
  device-mapper: message ioctl on LVM-I41GAeV8aoWdtFX92qXzNLTe1Cj3uWpaGpxBzy5dkJI623tV2r2yFSTgUVQ03yEe failed: Invalid argument


Version-Release number of selected component (if applicable):
3.10.0-419.el7.x86_64

lvm2-2.02.160-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
lvm2-libs-2.02.160-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
lvm2-cluster-2.02.160-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
device-mapper-1.02.130-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
device-mapper-libs-1.02.130-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
device-mapper-event-1.02.130-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
device-mapper-event-libs-1.02.130-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
device-mapper-persistent-data-0.6.2-0.1.rc8.el7    BUILT: Wed May  4 02:56:34 CDT 2016
cmirror-2.02.160-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
sanlock-3.3.0-1.el7    BUILT: Wed Feb 24 09:52:30 CST 2016
sanlock-lib-3.3.0-1.el7    BUILT: Wed Feb 24 09:52:30 CST 2016
lvm2-lockd-2.02.160-1.el7    BUILT: Wed Jul  6 11:16:47 CDT 2016
Comment 2 Heinz Mauelshagen 2016-07-18 18:23:28 UTC 
Already fixed with upstream commit c77c59f3d9a97b43cd2bd9be1c5892aea384f857
as commented in rhbz1354656
Comment 6 errata-xmlrpc 2016-11-04 04:22:16 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-2016-1445.html