Bug 1194464

Summary: raid4/5 creation now allows the -m option as well
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
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, rbednar, zkabelac
Version: 7.1   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.125-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 12:46:10 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 2015-02-19 21:28:49 UTC 
Description of problem:

# RHEL7.0 

[root@host-117 ~]# lvcreate --type raid4 -i 2 -m 2 -n myvol -L 600M vg
  Using default stripesize 64.00 KiB
  Mirror argument cannot be used with segment type, raid4
  Run `lvcreate --help' for more information.


# RHEL7.1 

[root@host-113 ~]# lvcreate --type raid4 -i 2 -m 2 -n myvol -L 600M vg
  Using default stripesize 64.00 KiB
  Logical volume "myvol" created.
[root@host-113 ~]# lvs -a -o +devices
  LV               VG   Attr       LSize   Cpy%Sync Devices
  myvol            vg   rwi-a-r--- 600.00m 100.00   myvol_rimage_0(0),myvol_rimage_1(0),myvol_rimage_2(0),myvol_rimage_3(0),myvol_rimage_4(0),myvol_rimage_5(0),myvol_rimage_6(0)
  [myvol_rimage_0] vg   iwi-aor--- 100.00m          /dev/sda1(1)
  [myvol_rimage_1] vg   iwi-aor--- 100.00m          /dev/sdb1(1)
  [myvol_rimage_2] vg   iwi-aor--- 100.00m          /dev/sdc1(1)
  [myvol_rimage_3] vg   iwi-aor--- 100.00m          /dev/sdd1(1)
  [myvol_rimage_4] vg   iwi-aor--- 100.00m          /dev/sde1(1)
  [myvol_rimage_5] vg   iwi-aor--- 100.00m          /dev/sdf1(1)
  [myvol_rimage_6] vg   iwi-aor--- 100.00m          /dev/sdg1(1)
  [myvol_rmeta_0]  vg   ewi-aor---   4.00m          /dev/sda1(0)
  [myvol_rmeta_1]  vg   ewi-aor---   4.00m          /dev/sdb1(0)
  [myvol_rmeta_2]  vg   ewi-aor---   4.00m          /dev/sdc1(0)
  [myvol_rmeta_3]  vg   ewi-aor---   4.00m          /dev/sdd1(0)
  [myvol_rmeta_4]  vg   ewi-aor---   4.00m          /dev/sde1(0)
  [myvol_rmeta_5]  vg   ewi-aor---   4.00m          /dev/sdf1(0)
  [myvol_rmeta_6]  vg   ewi-aor---   4.00m          /dev/sdg1(0)


Version-Release number of selected component (if applicable):
3.10.0-229.el7.x86_64
lvm2-2.02.115-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
lvm2-libs-2.02.115-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
lvm2-cluster-2.02.115-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
device-mapper-1.02.93-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
device-mapper-libs-1.02.93-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
device-mapper-event-1.02.93-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
device-mapper-event-libs-1.02.93-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
device-mapper-persistent-data-0.4.1-2.el7    BUILT: Wed Nov 12 12:39:46 CST 2014
cmirror-2.02.115-3.el7    BUILT: Wed Jan 28 09:59:01 CST 2015
Comment 1 Corey Marthaler 2015-02-19 21:34:39 UTC 
Appears to be another iteration of bug 842019 that was fixed in 6.4.
Comment 2 Peter Rajnoha 2015-06-17 09:13:56 UTC 
Should be fixed now, see also bug #1209445.
Comment 4 Roman Bednář 2015-09-14 12:04:49 UTC 
Marking as verified: 

[root@host-054 vedder-ng]# lvcreate --type raid4 -i 2 -m 2 -n myvol -L 600M vg
  Using default stripesize 64.00 KiB.
  Mirror argument cannot be used with segment type, raid4
  Run `lvcreate --help' for more information.

[root@host-054 vedder-ng]# lvcreate --type raid4 -m 2 -n myvol -L 600M vg
  Mirror argument cannot be used with segment type, raid4
  Run `lvcreate --help' for more information.

[root@host-054 vedder-ng]# lvcreate --type raid5 -m 2 -n myvol -L 600M vg
  Mirror argument cannot be used with segment type, raid5
  Run `lvcreate --help' for more information.

Verified with: 

3.10.0-315.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
Comment 5 errata-xmlrpc 2015-11-19 12:46:10 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