.TH VGSPLIT 8 "LVM TOOLS 2.03.11(2) (2021-01-08)" "Red Hat, Inc." .SH NAME vgsplit \- Move physical volumes into a new or existing volume group . .SH SYNOPSIS \fBvgsplit\fP \fIoption_args\fP \fIposition_args\fP .br [ \fIoption_args\fP ] .br .SH DESCRIPTION vgsplit moves one or more PVs from a source VG (the first VG arg) to a destination VG (the second VG arg). The PV(s) to move are named after the source and destination VGs, or an LV is named, in which case the PVs underlying the LV are moved. If the destination VG does not exist, a new VG is created (command options can be used to specify properties of the new VG, also see \fBvgcreate\fP(8).) LVs cannot be split between VGs; each LV must be entirely on the PVs in the source or destination VG. vgsplit can only move complete PVs. (See \fBpvmove\fP(8) for moving part of a PV.) .SH USAGE Split a VG by specified PVs. .br .P \fBvgsplit\fP \fIVG\fP \fIVG\fP \fIPV\fP ... .br .RS 4 [ COMMON_OPTIONS ] .RE .br Split a VG by PVs in a specified LV. .br .P \fBvgsplit\fP \fB\-n\fP|\fB\-\-name\fP \fILV\fP \fIVG\fP \fIVG\fP .br .RS 4 [ COMMON_OPTIONS ] .RE .br Common options for command: . .RS 4 .ad l [ \fB\-A\fP|\fB\-\-autobackup\fP \fBy\fP|\fBn\fP ] .ad b .br .ad l [ \fB\-l\fP|\fB\-\-maxlogicalvolumes\fP \fINumber\fP ] .ad b .br .ad l [ \fB\-p\fP|\fB\-\-maxphysicalvolumes\fP \fINumber\fP ] .ad b .br .ad l [ \fB\-M\fP|\fB\-\-metadatatype\fP \fBlvm2\fP ] .ad b .br .ad l [ \fB\-\-alloc\fP \fBcontiguous\fP|\fBcling\fP|\fBcling_by_tags\fP|\fBnormal\fP|\fBanywhere\fP|\fBinherit\fP ] .ad b .br .ad l [ \fB\-\-[vg]metadatacopies\fP \fBall\fP|\fBunmanaged\fP|\fINumber\fP ] .ad b .RE Common options for lvm: . .RS 4 .ad l [ \fB\-d\fP|\fB\-\-debug\fP ] .ad b .br .ad l [ \fB\-h\fP|\fB\-\-help\fP ] .ad b .br .ad l [ \fB\-q\fP|\fB\-\-quiet\fP ] .ad b .br .ad l [ \fB\-t\fP|\fB\-\-test\fP ] .ad b .br .ad l [ \fB\-v\fP|\fB\-\-verbose\fP ] .ad b .br .ad l [ \fB\-y\fP|\fB\-\-yes\fP ] .ad b .br .ad l [ \fB\-\-commandprofile\fP \fIString\fP ] .ad b .br .ad l [ \fB\-\-config\fP \fIString\fP ] .ad b .br .ad l [ \fB\-\-driverloaded\fP \fBy\fP|\fBn\fP ] .ad b .br .ad l [ \fB\-\-lockopt\fP \fIString\fP ] .ad b .br .ad l [ \fB\-\-longhelp\fP ] .ad b .br .ad l [ \fB\-\-nolocking\fP ] .ad b .br .ad l [ \fB\-\-profile\fP \fIString\fP ] .ad b .br .ad l [ \fB\-\-version\fP ] .ad b .RE .SH OPTIONS .HP .ad l \fB\-\-alloc\fP \fBcontiguous\fP|\fBcling\fP|\fBcling_by_tags\fP|\fBnormal\fP|\fBanywhere\fP|\fBinherit\fP .br Determines 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. \fBnormal\fP applies common sense rules such as not placing parallel stripes on the same PV. \fBinherit\fP applies the VG policy to an LV. \fBcontiguous\fP requires new PEs be placed adjacent to existing PEs. \fBcling\fP 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, \fBanywhere\fP 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 \fBlvm\fP(8) for more information about allocation. .ad b .HP .ad l \fB\-A\fP|\fB\-\-autobackup\fP \fBy\fP|\fBn\fP .br Specifies if metadata should be backed up automatically after a change. Enabling this is strongly advised! See \fBvgcfgbackup\fP(8) for more information. .ad b .HP .ad l \fB\-\-commandprofile\fP \fIString\fP .br The command profile to use for command configuration. See \fBlvm.conf\fP(5) for more information about profiles. .ad b .HP .ad l \fB\-\-config\fP \fIString\fP .br Config 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 \fBlvm.conf\fP(5) for more information about config. .ad b .HP .ad l \fB\-d\fP|\fB\-\-debug\fP ... .br 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). .ad b .HP .ad l \fB\-\-driverloaded\fP \fBy\fP|\fBn\fP .br If set to no, the command will not attempt to use device-mapper. For testing and debugging. .ad b .HP .ad l \fB\-h\fP|\fB\-\-help\fP .br Display help text. .ad b .HP .ad l \fB\-\-lockopt\fP \fIString\fP .br Used to pass options for special cases to lvmlockd. See \fBlvmlockd\fP(8) for more information. .ad b .HP .ad l \fB\-\-longhelp\fP .br Display long help text. .ad b .HP .ad l \fB\-l\fP|\fB\-\-maxlogicalvolumes\fP \fINumber\fP .br Sets the maximum number of LVs allowed in a VG. .ad b .HP .ad l \fB\-p\fP|\fB\-\-maxphysicalvolumes\fP \fINumber\fP .br Sets the maximum number of PVs that can belong to the VG. The value 0 removes any limitation. For large numbers of PVs, also see options \-\-pvmetadatacopies, and \-\-vgmetadatacopies for improving performance. .ad b .HP .ad l \fB\-M\fP|\fB\-\-metadatatype\fP \fBlvm2\fP .br Specifies the type of on-disk metadata to use. \fBlvm2\fP (or just \fB2\fP) is the current, standard format. \fBlvm1\fP (or just \fB1\fP) is no longer used. .ad b .HP .ad l \fB\-n\fP|\fB\-\-name\fP \fIString\fP .br Move only PVs used by the named LV. .ad b .HP .ad l \fB\-\-nolocking\fP .br Disable locking. .ad b .HP .ad l \fB\-\-profile\fP \fIString\fP .br An alias for \-\-commandprofile or \-\-metadataprofile, depending on the command. .ad b .HP .ad l \fB\-q\fP|\fB\-\-quiet\fP ... .br Suppress output and log messages. Overrides \-\-debug and \-\-verbose. Repeat once to also suppress any prompts with answer 'no'. .ad b .HP .ad l \fB\-t\fP|\fB\-\-test\fP .br Run 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. .ad b .HP .ad l \fB\-v\fP|\fB\-\-verbose\fP ... .br Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and stderr. .ad b .HP .ad l \fB\-\-version\fP .br Display version information. .ad b .HP .ad l \fB\-\-[vg]metadatacopies\fP \fBall\fP|\fBunmanaged\fP|\fINumber\fP .br Number of copies of the VG metadata that are kept. VG metadata is kept in VG metadata areas on PVs in the VG, i.e. reserved space at the start and/or end of the PVs. Keeping a copy of the VG metadata on every PV can reduce performance in VGs containing a large number of PVs. When this number is set to a non-zero value, LVM will automatically choose PVs on which to store metadata, using the metadataignore flags on PVs to achieve the specified number. The number can also be replaced with special string values: \fBunmanaged\fP causes LVM to not automatically manage the PV metadataignore flags. \fBall\fP causes LVM to first clear the metadataignore flags on all PVs, and then to become unmanaged. .ad b .HP .ad l \fB\-y\fP|\fB\-\-yes\fP .br Do not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see \-qq.) .ad b .SH VARIABLES .HP \fIVG\fP .br Volume Group name. See \fBlvm\fP(8) for valid names. .HP \fIPV\fP .br Physical 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): \fIPV\fP[\fB:\fP\fIPE\fP\fB\-\fP\fIPE\fP]... Start and length range (counting from 0): \fIPV\fP[\fB:\fP\fIPE\fP\fB+\fP\fIPE\fP]... .HP \fIString\fP .br See the option description for information about the string content. .HP \fISize\fP[UNIT] .br 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: \fBbBsSkKmMgGtTpPeE\fP. b|B is bytes, s|S is sectors of 512 bytes, k|K is KiB, m|M is MiB, g|G is GiB, t|T is TiB, p|P is PiB, e|E is EiB. (This should not be confused with the output control \-\-units, where capital letters mean multiple of 1000.) .SH ENVIRONMENT VARIABLES See \fBlvm\fP(8) for information about environment variables used by lvm. For example, LVM_VG_NAME can generally be substituted for a required VG parameter. .SH SEE ALSO .BR lvm (8) .BR lvm.conf (5) .BR lvmconfig (8) .BR pvchange (8) .BR pvck (8) .BR pvcreate (8) .BR pvdisplay (8) .BR pvmove (8) .BR pvremove (8) .BR pvresize (8) .BR pvs (8) .BR pvscan (8) .BR vgcfgbackup (8) .BR vgcfgrestore (8) .BR vgchange (8) .BR vgck (8) .BR vgcreate (8) .BR vgconvert (8) .BR vgdisplay (8) .BR vgexport (8) .BR vgextend (8) .BR vgimport (8) .BR vgimportclone (8) .BR vgmerge (8) .BR vgmknodes (8) .BR vgreduce (8) .BR vgremove (8) .BR vgrename (8) .BR vgs (8) .BR vgscan (8) .BR vgsplit (8) .BR lvcreate (8) .BR lvchange (8) .BR lvconvert (8) .BR lvdisplay (8) .BR lvextend (8) .BR lvreduce (8) .BR lvremove (8) .BR lvrename (8) .BR lvresize (8) .BR lvs (8) .BR lvscan (8) .BR lvm-fullreport (8) .BR lvm-lvpoll (8) .BR lvm2\-activation\-generator (8) .BR blkdeactivate (8) .BR lvmdump (8) .BR dmeventd (8) .BR lvmpolld (8) .BR lvmlockd (8) .BR lvmlockctl (8) .BR cmirrord (8) .BR lvmdbusd (8) .BR lvmsystemid (7) .BR lvmreport (7) .BR lvmraid (7) .BR lvmthin (7) .BR lvmcache (7)