|PVMOVE(8)||System Manager's Manual||PVMOVE(8)|
[ option_args ]
[ position_args ]
[ -A|--autobackup y|n ][ -n|--name LV ][ --alloc contiguous|cling|cling_by_tags|normal| anywhere| inherit ][ --atomic ][ --noudevsync ][ --reportformat basic|json ][ COMMON_OPTIONS ]
[ PV ... ]Continue or abort existing pvmove operations.
[ COMMON_OPTIONS ]
[ -b|--background ][ -i|--interval Number ][ --abort ]Common options for lvm:
[ -d|--debug ][ -h|--help ][ -q|--quiet ][ -t|--test ][ -v|--verbose ][ -y|--yes ][ --commandprofile String ][ --config String ][ --driverloaded y|n ][ --lockopt String ][ --longhelp ][ --profile String ][ --version ]
--abortAbort any pvmove operations in progress. If a pvmove was started with the --atomic option, then all LVs will remain on the source PV. Otherwise, segments that have been moved will remain on the destination PV, while unmoved segments will remain on the source PV.
--alloc contiguous|cling|cling_by_tags| normal|anywhere| inheritDetermines the allocation policy when a command needs to allocate Physical Extents (PEs) from the VG. Each VG and LV has an allocation policy which can be changed with vgchange/lvchange, or overriden on the command line. normal applies common sense rules such as not placing parallel stripes on the same PV. inherit applies the VG policy to an LV. contiguous requires new PEs be placed adjacent to existing PEs. cling places new PEs on the same PV as existing PEs in the same stripe of the LV. If there are sufficient PEs for an allocation, but normal does not use them, anywhere will use them even if it reduces performance, e.g. by placing two stripes on the same PV. Optional positional PV args on the command line can also be used to limit which PVs the command will use for allocation. See lvm(8) for more information about allocation.
--atomicMakes a pvmove operation atomic, ensuring that all affected LVs are moved to the destination PV, or none are if the operation is aborted.
-A|--autobackup y|nSpecifies if metadata should be backed up automatically after a change. Enabling this is strongly advised! See vgcfgbackup(8) for more information.
-b|--backgroundIf the operation requires polling, this option causes the command to return before the operation is complete, and polling is done in the background.
--commandprofile StringThe command profile to use for command configuration. See lvm.conf(5) for more information about profiles.
--config StringConfig settings for the command. These override lvm.conf settings. The String arg uses the same format as lvm.conf, or may use section/field syntax. See lvm.conf(5) for more information about config.
-d|--debug ...Set debug level. Repeat from 1 to 6 times to increase the detail of messages sent to the log file and/or syslog (if configured).
--driverloaded y|nIf set to no, the command will not attempt to use device-mapper. For testing and debugging.
-h|--helpDisplay help text.
-i|--interval NumberReport progress at regular intervals.
--lockopt StringUsed to pass options for special cases to lvmlockd. See lvmlockd(8) for more information.
--longhelpDisplay long help text.
-n|--name StringMove only the extents belonging to the named LV.
--noudevsyncDisables udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. Only use this if udev is not running or has rules that ignore the devices LVM creates.
--profile StringAn alias for --commandprofile or --metadataprofile, depending on the command.
-q|--quiet ...Suppress output and log messages. Overrides --debug and --verbose. Repeat once to also suppress any prompts with answer 'no'.
--reportformat basic|jsonOverrides current output format for reports which is defined globally by the report/output_format setting in lvm.conf. basic is the original format with columns and rows. If there is more than one report per command, each report is prefixed with the report name for identification. json produces report output in JSON format. See lvmreport(7) for more information.
-t|--testRun in test mode. Commands will not update metadata. This is implemented by disabling all metadata writing but nevertheless returning success to the calling function. This may lead to unusual error messages in multi-stage operations if a tool relies on reading back metadata it believes has changed but hasn't.
-v|--verbose ...Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr.
--versionDisplay version information.
-y|--yesDo not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)
PVPhysical Volume name, a device path under /dev. For commands managing physical extents, a PV positional arg generally accepts a suffix indicating a range (or multiple ranges) of physical extents (PEs). When the first PE is omitted, it defaults to the start of the device, and when the last PE is omitted it defaults to end. Start and end range (inclusive): PV[:PE-PE]... Start and length range (counting from 0): PV[:PE+PE]...
StringSee the option description for information about the string content.
Size[UNIT]Size is an input number that accepts an optional unit. Input units are always treated as base two values, regardless of capitalization, e.g. 'k' and 'K' both refer to 1024. The default input unit is specified by letter, followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE. b|B is bytes, s|S is sectors of 512 bytes, k|K is kilobytes, m|M is megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes, e|E is exabytes. (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)lvm(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter. vgconvert(8). If the --atomic option is used, a slightly different approach is used for the move. Again, a temporary 'pvmove' LV is created to store the details of all the data movements required. This temporary LV contains all the segments of the various LVs that need to be moved. However, in this case, an identical LV is allocated that contains the same number of segments and a mirror is created to copy the contents from the first temporary LV to the second. After a complete copy is made, the temporary LVs are removed, leaving behind the segments on the destination PV. If an abort is issued during the move, all LVs being moved will remain on the source PV.
|LVM TOOLS 2.02.183(2) (2018-12-07)||Red Hat, Inc.|