Bug 1191630
| Summary: | LVM RAID - Add support for raid level takeover (part 1) | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Heinz Mauelshagen <heinzm> | |
| Component: | lvm2 | Assignee: | Heinz Mauelshagen <heinzm> | |
| lvm2 sub component: | Mirroring and RAID | QA Contact: | cluster-qe <cluster-qe> | |
| Status: | CLOSED ERRATA | Docs Contact: | Milan Navratil <mnavrati> | |
| Severity: | unspecified | |||
| Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, lkuprova, mnavrati, msnitzer, prajnoha, prockai, zkabelac | |
| Version: | 7.2 | Keywords: | TechPreview | |
| Target Milestone: | rc | Flags: | heinzm:
needinfo-
|
|
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | lvm2-2.02.163-1.el7 | Doc Type: | Technology Preview | |
| Doc Text: |
`LVM` RAID-level takeover is now available
RAID-level takeover, the ability to switch between RAID types, is now available as a Technology Preview. With RAID-level takeover, the user can decide based on their changing hardware characteristics what type of RAID configuration best suits their needs and make the change without having to deactivate the logical volume. For example, if a `striped` logical volume is created, it can be later converted to a RAID4 logical volume if an additional device is available.
Starting with Red Hat Enterprise Linux 7.3, the following conversions are available as a Technology Preview:
* striped <-> RAID4
* linear <-> RAID1
* mirror <-> RAID1 (mirror is a legacy type, but still supported)
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1366296 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-04 04:09:02 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 834579, 1189124, 1346081, 1366296 | |||
|
Description
Heinz Mauelshagen
2015-02-11 15:59:44 UTC
Code's done and in review/integration. An exhaustive compliment of conversions did not make the cut-off for this release. A partial list of conversions did, they include: conversions between any of: striped, raid0, raid0_meta, raid4 conversions between any of: linear, raid1, mirror The LVM team will implement test to validate all of these conversions as part of their regression test suite. QA will please ensure (along with any other test) the consistency and coherency of the data through these conversions. Take-overs (conversions from one RAID type to another) can be performed with the 'lvconvert' command, as follows: # lvconvert --type <new_type> VG/lv_of_old_type raid5 and raid6 were not included at this point. The first takeover attempt I tried doesn't appear to have been laid out properly. Is this actually what's expected when going from raid0 -> raid4?
[root@host-083 ~]# vgcreate test /dev/sd[abcdefgh]1
Physical volume "/dev/sdb1" successfully created.
Volume group "test" successfully created
[root@host-083 ~]# pvscan
PV /dev/sda1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdc1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdd1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sde1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdf1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdg1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdh1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
PV /dev/sdb1 VG test lvm2 [24.99 GiB / 24.99 GiB free]
[root@host-083 ~]# lvcreate --type raid0 -L 100M -i 2 -n LV test
Using default stripesize 64.00 KiB.
Rounding size 100.00 MiB (25 extents) up to stripe boundary size 104.00 MiB (26 extents).
Logical volume "LV" created.
[root@host-083 ~]# lvs -a -o +devices
LV VG Attr LSize Log Cpy%Sync Devices
LV test rwi-a-r--- 104.00m LV_rimage_0(0),LV_rimage_1(0)
[LV_rimage_0] test iwi-aor--- 52.00m /dev/sda1(0)
[LV_rimage_1] test iwi-aor--- 52.00m /dev/sdc1(0)
[root@host-083 ~]# lvconvert --type raid4 test/LV
Using default stripesize 64.00 KiB.
Logical volume test/LV successfully converted.
[root@host-083 ~]# lvs -a -o +devices
LV VG Attr LSize Log Cpy%Sync Devices
LV test rwi-a-r--- 104.00m 100.00 LV_rimage_0(0),LV_rimage_1(0),LV_rimage_2(0)
[LV_rimage_0] test iwi-aor--- 52.00m /dev/sda1(0)
[LV_rimage_0_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(13)
[LV_rimage_1] test iwi-aor--- 52.00m /dev/sdc1(0)
[LV_rimage_1_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(14)
[LV_rimage_2] test iwi-aor--- 52.00m /dev/sdd1(1)
[LV_rmeta_0] test ewi-aor--- 4.00m /dev/sdd1(0)
[root@host-083 ~]# lvcreate -i 2 --type raid4 -n LV2 test -L 100M
Using default stripesize 64.00 KiB.
Rounding size 100.00 MiB (25 extents) up to stripe boundary size 104.00 MiB (26 extents).
Logical volume "LV2" created.
[root@host-083 ~]# lvs -a -o +devices
LV VG Attr LSize Log Cpy%Sync Devices
LV test rwi-a-r--- 104.00m 100.00 LV_rimage_0(0),LV_rimage_1(0),LV_rimage_2(0)
[LV_rimage_0] test iwi-aor--- 52.00m /dev/sda1(0)
[LV_rimage_0_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(13)
[LV_rimage_1] test iwi-aor--- 52.00m /dev/sdc1(0)
[LV_rimage_1_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(14) <- why is sda being used in an rimage1 device?
[LV_rimage_2] test iwi-aor--- 52.00m /dev/sdd1(1)
[LV_rmeta_0] test ewi-aor--- 4.00m /dev/sdd1(0) <- why is sdd being used in an rimage0 device?
# Also, where is the rmeta volume for rimage2?
# The above converted "raid4" volume looks nothing like and is laid out unlike the initially created raid4 volume below:
LV2 test rwi-a-r--- 104.00m 100.00 LV2_rimage_0(0),LV2_rimage_1(0),LV2_rimage_2(0)
[LV2_rimage_0] test iwi-aor--- 52.00m /dev/sda1(16)
[LV2_rimage_1] test iwi-aor--- 52.00m /dev/sdc1(14)
[LV2_rimage_2] test iwi-aor--- 52.00m /dev/sdd1(15)
[LV2_rmeta_0] test ewi-aor--- 4.00m /dev/sda1(15)
[LV2_rmeta_1] test ewi-aor--- 4.00m /dev/sdc1(13)
[LV2_rmeta_2] test ewi-aor--- 4.00m /dev/sdd1(14)
3.10.0-489.el7.x86_64
lvm2-2.02.163-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
lvm2-libs-2.02.163-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
lvm2-cluster-2.02.163-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
device-mapper-1.02.133-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
device-mapper-libs-1.02.133-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
device-mapper-event-1.02.133-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
device-mapper-event-libs-1.02.133-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016
cmirror-2.02.163-1.el7 BUILT: Wed Aug 10 06:53:21 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.163-1.el7 BUILT: Wed Aug 10 06:53:21 CDT 2016
The double suffix on the internal rmeta LVs is just cosmetic - fixed with https://git.fedorahosted.org/cgit/lvm2.git/commit/ https://www.redhat.com/archives/lvm-devel/2016-August/msg00063.html Filed bug 1366737, bug 1366738, and bug 1366739 for the issues listed above in comment #6. Additional take over bugs: bug 1366749, bug 1366752, bug 1366760 Marking verified for TechPreview in the latest rpms. Applicable raid and mirror regression tests passed when run on raid/mirror converted volumes. 3.10.0-510.el7.x86_64 lvm2-2.02.166-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 lvm2-libs-2.02.166-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 lvm2-cluster-2.02.166-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 device-mapper-1.02.135-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 device-mapper-libs-1.02.135-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 device-mapper-event-1.02.135-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 device-mapper-event-libs-1.02.135-1.el7 BUILT: Wed Sep 28 02:26:52 CDT 2016 device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016 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 |