Difference between revisions of "Lvextend"
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
== Related commands == | == Related commands == | ||
+ | * <code>--LV-expand</code> option from [[virt-resize]] | ||
* <code>[[umount]]</code> | * <code>[[umount]]</code> | ||
* <code>[[fuser]]</code> | * <code>[[fuser]]</code> |
Revision as of 07:42, 5 August 2020
This article is a Draft. Help us to complete it.
Options:
-r, --resizefs
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_hphq1 have changed sizes. New size given (524287 extents) not larger than existing size (1048576 extents)
Related commands
--LV-expand
option from virt-resizeumount
fuser
pvresize
lvresize
vgextend
virt-resize
fdisk
Activities
See also
- 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
Advertising: