Red Hat Bugzilla – Bug 1394048
LVM RAID: Ability to reduce the size of a RAID LV
Last modified: 2017-08-01 17:49:49 EDT
Currently, it is not possible to reduce the size of a RAID 4/5/6 LV. This bug is a feature request to add that ability.
Prepared for review/integration as lvresize/lvreduce functionality on lvm2 upstream branch dev-lvmguy-raid-takeover-reshape-resize_work
Upstream commit 55eaabd1183042b8e03b3a969eadf624623c4b62
Verified with latest rpms, ability to reduce size of raid has been added. Tested with raid0, raid1, raid4, raid5, raid6 and raid10. # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel_virt-145 -wi-ao---- 6.70g swap rhel_virt-145 -wi-ao---- 876.00m raid0 vg rwi-a-r--- 1.00g raid1 vg rwi-a-r--- 1.00g 100.00 raid10 vg rwi-a-r--- 1.00g 100.00 raid4 vg rwi-a-r--- 1.00g 100.00 raid5 vg rwi-a-r--- 1.00g 100.00 raid6 vg rwi-a-r--- 1.01g 100.00 # for i in raid0 raid1 raid4 raid5 raid6 raid10; do lvreduce -L500M vg/$i --force;done WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid0 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid0 successfully resized. WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid1 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid1 successfully resized. WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid4 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid4 successfully resized. WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid5 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid5 successfully resized. WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid6 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid6 successfully resized. WARNING: Reducing active logical volume to 500.00 MiB. THIS MAY DESTROY YOUR DATA (filesystem etc.) Size of logical volume vg/raid10 changed from 1.00 GiB (256 extents) to 500.00 MiB (125 extents). Logical volume vg/raid10 successfully resized. # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root rhel_virt-145 -wi-ao---- 6.70g swap rhel_virt-145 -wi-ao---- 876.00m raid0 vg rwi-a-r--- 504.00m raid1 vg rwi-a-r--- 500.00m 100.00 raid10 vg rwi-a-r--- 504.00m 100.00 raid4 vg rwi-a-r--- 504.00m 100.00 raid5 vg rwi-a-r--- 504.00m 100.00 raid6 vg rwi-a-r--- 504.00m 100.00 3.10.0-640.el7.x86_64 lvm2-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 lvm2-libs-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 lvm2-cluster-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 device-mapper-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 device-mapper-libs-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 device-mapper-event-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 device-mapper-event-libs-1.02.138-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017 device-mapper-persistent-data-0.7.0-0.1.rc6.el7 BUILT: Mon Mar 27 17:15:46 CEST 2017 cmirror-2.02.169-3.el7 BUILT: Wed Mar 29 16:17:46 CEST 2017
jbrassow: As per our IRC discussion, I have marked this BZ for inclusion in the 7.4 release notes and I have written up a description. Can you check that over to be sure it's correct? Steven
(In reply to Steven J. Levine from comment #10) > jbrassow: > > As per our IRC discussion, I have marked this BZ for inclusion in the 7.4 > release notes and I have written up a description. Can you check that over > to be sure it's correct? > > Steven yes, looks fine. A user can reduce the size of a RAID LV with 'lvreduce' or 'lvresize'.
I added lvresize to the description for the release notes.
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