Difference between revisions of "Lvextend"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
One or more devices used as PVs in VG data_hphq1 have changed sizes. | 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) | New size given (524287 extents) not larger than existing size (1048576 extents) | ||
| + | |||
| + | |||
| + | lvextend -l 100%FREE -n /dev/mapper/VG_NAME-LV_NAME | ||
| + | New size given (26214 extents) not larger than existing size (1048576 [[extents]]) | ||
| + | |||
== Activities == | == Activities == | ||
Revision as of 11:26, 7 January 2020
This article is a Draft. Help us to complete it.
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)
lvextend -l 100%FREE -n /dev/mapper/VG_NAME-LV_NAME New size given (26214 extents) not larger than existing size (1048576 extents)
Activities
See also
- scan:
pvscanvgscan - LVM:
lvslvmscanlvm fullreportlvmreportlvmconfiglvmdumplvmchecklvm dumpconfig - Scan:
pvsvgslvspvscanvgscan - PV:
pvcreatepvremovepvscanpvremovepvscanpvspvchangepvckpvdisplaypvresize - LV:
lvdisplaylvcreatelvremove,lvresize,lvextend,lvreduce,lvrename - VG:
vgdisplay,vgcreate,vgremove,vgextend,vgreduce,vgscan,vgchange,vgrename,vgcfgbackup,vgcfgrestore,vgimportclone,vgck - Check commands:
pvckvgck
Advertising:
