PVCHANGE(8)

NAME
pvresize - resize a physical volume in a volume group

SYNOPSIS
pvresize [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-s|--sizePhysicalVolumeSize[kKmMgGtT]] [-v|--verbose] [--version] PhysicalVolume [PhysicalVolume...]

DESCRIPTION
pvresize allows you to change the size of a physical volume which belongs to a volume group in case the underlying device changes size. Examples are hardware RAID systems which allow resizing without data loss or size changes on loop devices. The volume group must be inactive to run this command.

  OPTIONS

-A, --autobackup y/n
    Controls automatic backup of VG metadata after the resize ( see vgcfgbackup(8) ). Default is yes.

-d, --debug
    Enables additional debugging output (if compiled with DEBUG).

-h, --help
    Print a usage message on standard output and exit successfully.

-s, --size
    Overrides the size of the physical volume which is normally retrieved. Useful in rare case where this value is wrong. More useful to fake large physical volumes of up to 2 Terabyes - 1 Kilobyte on smaller devices for testing purposes only where no real access to data in created logical volumes is needed. If you wish to create the supported maximum, use "pvcreate -s 2147483647k PhysicalVolume [PhysicalVolume ...]". All other LVM tools will use this size with the exception of lvmdiskscan(8)

-v, --verbose
    Gives verbose runtime information about pvresize's activities.

Example
"pvresize /dev/sdk1" resizes physical volume in /dev/sdk1 to the size
    the operating system reports.

DIAGNOSTICS
pvresize returns an exit code of 0 for success and > 0 for error:
1  no physical volume name(s) on command line
2  invalid physical volume name
3  error writing VGDA to physical volumes
4  error doing backup of VGDA to disk
5  error storing VGDA in lvmtab
95 driver/module not in kernel
96 invalid I/O protocol version
97 error locking logical volume manager
98 invalid lvmtab (run vgscan(8))
99 invalid command line

ENVIRONMENT VARIABLES

LVM_AUTOARCHIVE
    If this variable is set to "no" then the automatic backup of VG metadata is turned off.

LVM_MAX_ARCHIVES
    This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number between 0 and 999. The higher this number is, the more changes you can restore using vgcfgrestore(8).

See also
lvm(8), pvchange(8), pvcreate(8), pvmove(8)

AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>