|VGSPLIT(8)||System Manager's Manual||VGSPLIT(8)|
[ option_args ]
[ COMMON_OPTIONS ]
[ COMMON_OPTIONS ]
[ -A|--autobackup y|n ][ -c|--clustered y|n ][ -l|--maxlogicalvolumes Number ][ -p|--maxphysicalvolumes Number ][ -M|--metadatatype lvm2 ][ --alloc contiguous|cling|cling_by_tags|normal| anywhere| inherit ][ --[vg]metadatacopies all|unmanaged|Number ]
[ -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 ]
--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.
-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.
-c|--clustered y|nSpecifies the clustered property of the new VG.
--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.
--lockopt StringUsed to pass options for special cases to lvmlockd. See lvmlockd(8) for more information.
--longhelpDisplay long help text.
-l|--maxlogicalvolumes NumberSets the maximum number of LVs allowed in a VG.
-p|--maxphysicalvolumes NumberSets 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.
-M|--metadatatype lvm2Specifies the type of on-disk metadata to use. lvm2 (or just 2) is the current, standard format. lvm1 (or just 1) is no longer used.
-n|--name StringMove only PVs used by the named LV.
--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'.
-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.
--[vg]metadatacopies all|unmanaged|NumberNumber 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: unmanaged causes LVM to not automatically manage the PV metadataignore flags. all causes LVM to first clear the metadataignore flags on all PVs, and then to become unmanaged.
-y|--yesDo not prompt for confirmation interactively but always assume the answer yes. Use with extreme caution. (For automatic no, see -qq.)
VGVolume Group name. See lvm(8) for valid names.
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. lvm(8) lvm.conf(5) lvmconfig(8)
|LVM TOOLS 2.02.182(2) (2018-10-30)||Red Hat, Inc.|