Lvextend

This article is a Draft. Help us to complete it.

Options:

-r, --resizefs 

lvextend -l +100%FREE -n /dev/mapper/ubuntu--vg-ubuntu--lv
  Size of logical volume ubuntu-vg/ubuntu-lv changed from 63.50 GiB (16256 extents) to <127.00 GiB (32511 extents).
  Logical volume ubuntu-vg/ubuntu-lv successfully resized.

Note: + sign
lvextend -l +100%FREE -n /dev/mapper/VG_NAME-LV_NAME
 Size of logical volume VG_NAME/LV_NAME changed from 4.00 TiB (1048576 extents) to <4.10 TiB (1074790 extents).
 Logical volume VG_NAME/LV_NAME successfully resized.

lvextend -l 100%FREE -n /dev/mapper/VG_NAME-LV_NAME
 New size given (26214 extents) not larger than existing size (1048576 extents)

 lvextend -l +100%FREE -n /dev/main/LV_NAME
 New size (23736 extents) matches existing size (23736 extents).

lvextend -l 100%FREE -n /dev/mapper/VG_NAME-LV_NAME
 WARNING: Device /dev/mapper/3600a09803831417a5a244f5665797a4d has size of 8804682957 sectors which is smaller than corresponding PV size of 12884901888 sectors. Was device resized?
 One or more devices used as PVs in VG data_server1 have changed sizes.
 New size given (524287 extents) not larger than existing size (1048576 extents)

Related commands

• --LV-expand option from virt-resize
• umount
• fuser
• pvresize
• lvresize
• vgextend
• resize2fs
• fdisk

Activities

1. Extend LVM on qcow2 images

See also

• LVM: LVM errors LVM scan commands lkvmetad, Add a new disk

scan: pvscan vgscan

LVM: lvs lvmscan lvm fullreport lvmreport lvmconfig lvmdump lvmcheck lvm dumpconfig

Scan: pvs vgs lvs pvscan vgscan

PV: pvcreate pvremove pvscan pvremove pvscan pvs pvchange pvck pvdisplay pvresize

LV: lvdisplay lvcreate lvremove, lvresize, lvextend, lvreduce, lvrename

VG: vgdisplay,vgcreate,vgremove, vgextend, vgreduce, vgscan, vgchange, vgrename, vgcfgbackup, vgcfgrestore, vgimportclone, vgck

Check commands: pvck vgck