Changes between Version 4 and Version 5 of extend-logical-volume


Ignore:
Timestamp:
Sep 9, 2020, 10:46:24 PM (2 weeks ago)
Author:
JaimeV
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • extend-logical-volume

    v4 v5  
    7272If you do not see enough VFree space, you'll need to follow the instructions on [wiki:extend-disk-on-kvm-guest].
    7373
     74Also 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{{{
     770 stone:~# pvs
     78  PV         VG        Fmt  Attr PSize    PFree
     79  /dev/vda2  vg_stone0 lvm2 a--  <249.76g 78.80g
     80}}}
     81
    7482 == Step Two: Extend the logical volume ==
    7583
    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.
    7785
    7886{{{
    79 # lvextend --size 10GB /dev/mapper/vg_stone0-var
     87# lvextend --size 10GB /dev/mapper/vg_stone0-var /dev/vda2
    8088}}}
    8189
    82 Make sure that the number after --size is the total size of the logical volume you want.
    8390
    8491=== Resizing cached logical volumes ===