Changes between Version 4 and Version 5 of extend-logical-volume
- Timestamp:
- Sep 10, 2020, 2:46:24 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
extend-logical-volume
v4 v5 72 72 If you do not see enough VFree space, you'll need to follow the instructions on [wiki:extend-disk-on-kvm-guest]. 73 73 74 Also check which physical device(s) are assigned to your logical volume group. On servers using [https://support.mayfirst.org/wiki/lvm-cache lvm caching] more than on physical device may be assigned to the same volume group. 75 76 {{{ 77 0 stone:~# pvs 78 PV VG Fmt Attr PSize PFree 79 /dev/vda2 vg_stone0 lvm2 a-- <249.76g 78.80g 80 }}} 81 74 82 == Step Two: Extend the logical volume == 75 83 76 Once you've done that, then execute the following command for the logical volume. 84 Once you've done that, then execute the following command for the logical volume. Make sure that the number after --size is the total size of the logical volume you want. In the below example /dev/vda2 is the physical volume based on spinning disk used for volume group vg_stone0. When extending logical volumes for servers that have lvm cache enabled we want to be sure that the extents for the space we add come from the physical device based on spinning disk. 77 85 78 86 {{{ 79 # lvextend --size 10GB /dev/mapper/vg_stone0-var 87 # lvextend --size 10GB /dev/mapper/vg_stone0-var /dev/vda2 80 88 }}} 81 89 82 Make sure that the number after --size is the total size of the logical volume you want.83 90 84 91 === Resizing cached logical volumes ===