Description of problem:
lvm2 is missing RAID0 support based on the MD RAID0 personality
Steps to Reproduce:
1. lvcreate --type raid0 -l1 -i2 -nr $VG
Succeeds creating a reid0 mapping
lvm2 tools/lib need 'raid0' segment type added using a respective enhancement to the dm-raid target (see seperate kernel bz) which shall utilize the MD 'raid0' personality.
The mandatory allocation of internal metadata LVs (aka rmeta LVs) as with the already supported MD-based raid levels (RAID1/10/4/5/6) shall be optional, because the MD 'raid0' personality does _not_ require metadata devices unless a takeover from 'raid0' to 'raid5' is requested. The distinction between 'raid0' LVs with and without metadata LVs may be based on the segement type name (e.g. segment type name 'raid0' -> no internal metadata LVs vs. 'raid0_meta' -> allocate internal metadata LVs)
Didn't make 7.2 devel freeze. Will include this with the reshaping patches for 7.3.
Support for raid0 and raid0_meta segments included in 2.02.159.
All applicable raid test cases have been tried and passed on raid0, as well as in exclusive mode for both clvmd and lvmlockd mode.
lvm2-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
lvm2-libs-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
lvm2-cluster-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-event-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-event-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016
cmirror-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
sanlock-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016
sanlock-lib-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016
lvm2-lockd-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016
bug 1367223 should really block this feature.
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.