Ubuntu Manpage: vgsplit - Move physical volumes into a new or existing volume group

Provided by: lvm2_2.03.11-2.1ubuntu5_amd64

NAME

       vgsplit - Move physical volumes into a new or existing volume group

SYNOPSIS

       vgsplit option_args position_args
           [ option_args ]

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 vgcreate(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 pvmove(8) for moving part of a PV.)

USAGE

       Split a VG by specified PVs.

       vgsplit VG VG PV ...
           [ COMMON_OPTIONS ]

       Split a VG by PVs in a specified LV.

       vgsplit -n|--name LV VG VG
           [ COMMON_OPTIONS ]

       Common options for command:
           [ -A|--autobackup 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 ]

       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 ]
           [    --nolocking ]
           [    --profile String ]
           [    --version ]

OPTIONS

--alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit
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. 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|n
Specifies if metadata should be backed up automatically after a change. Enabling this is strongly
advised! See vgcfgbackup(8) for more information.

--commandprofile String
The command profile to use for command configuration. See lvm.conf(5) for more information about
profiles.

--config String
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 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|n
If set to no, the command will not attempt to use device-mapper. For testing and debugging.

-h|--help
Display help text.

--lockopt String
Used to pass options for special cases to lvmlockd. See lvmlockd(8) for more information.

--longhelp
Display long help text.

-l|--maxlogicalvolumes Number
Sets the maximum number of LVs allowed in a VG.

-p|--maxphysicalvolumes Number
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.

-M|--metadatatype lvm2
Specifies 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 String
Move only PVs used by the named LV.

--nolocking
Disable locking.

--profile String
An 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|--test
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.

-v|--verbose ...
Set verbose level. Repeat from 1 to 4 times to increase the detail of messages sent to stdout and
stderr.

--version
Display version information.

--[vg]metadatacopies all|unmanaged|Number
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: 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|--yes
Do not prompt for confirmation interactively but always assume the answer yes. Use with extreme
caution. (For automatic no, see -qq.)

VARIABLES

       VG
              Volume Group name.  See lvm(8) for valid names.

       PV
              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): PV[:PE-PE]...  Start  and
              length range (counting from 0): PV[:PE+PE]...

       String
              See 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 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.)

ENVIRONMENT VARIABLES

       See lvm(8) for information about environment  variables  used  by  lvm.   For  example,  LVM_VG_NAME  can
       generally be substituted for a required VG parameter.