vgsplit(8)

1VGSPLIT(8)                  System Manager's Manual                 VGSPLIT(8)
2
3
4

NAME

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

SYNOPSIS

9       vgsplit option_args position_args
10           [ option_args ]
11

DESCRIPTION

13       vgsplit moves one or more PVs from a source VG to a destination VG. The
14       PVs can be specified explicitly or implicitly by naming an LV, in which
15       case on PVs underlying the LV are moved.
16
17       If  the  destination  VG  does  not exist, a new VG is created (command
18       options can be used to specify properties  of  the  new  VG,  also  see
19       vgcreate(8).)
20
21       LVs cannot be split between VGs; each LV must be entirely on the PVs in
22       the source or destination VG.
23
24       vgsplit can only move complete PVs. (See pvmove(8) for moving part of a
25       PV.)
26

USAGE

28       Split a VG by specified PVs.
29
30       vgsplit VG VG PV ...
31           [ COMMON_OPTIONS ]
32
33       Split a VG by PVs in a specified LV.
34
35       vgsplit -n|--name LV VG VG
36           [ COMMON_OPTIONS ]
37
38       Common options for command:
39           [ -A|--autobackup y|n ]
40           [ -c|--clustered y|n ]
41           [ -l|--maxlogicalvolumes Number ]
42           [ -p|--maxphysicalvolumes Number ]
43           [ -M|--metadatatype lvm2 ]
44           [    --alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit
45           ]
46           [    --[vg]metadatacopies all|unmanaged|Number ]
47
48       Common options for lvm:
49           [ -d|--debug ]
50           [ -h|--help ]
51           [ -q|--quiet ]
52           [ -t|--test ]
53           [ -v|--verbose ]
54           [ -y|--yes ]
55           [    --commandprofile String ]
56           [    --config String ]
57           [    --driverloaded y|n ]
58           [    --lockopt String ]
59           [    --longhelp ]
60           [    --profile String ]
61           [    --version ]
62

OPTIONS

64       --alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit
65              Determines the allocation policy when a command needs to allo‐
66              cate Physical Extents (PEs) from the VG. Each VG and LV has an
67              allocation policy which can be changed with vgchange/lvchange,
68              or overriden on the command line.  normal applies common sense
69              rules such as not placing parallel stripes on the same PV.
70              inherit applies the VG policy to an LV.  contiguous requires new
71              PEs be placed adjacent to existing PEs.  cling places new PEs on
72              the same PV as existing PEs in the same stripe of the LV.  If
73              there are sufficient PEs for an allocation, but normal does not
74              use them, anywhere will use them even if it reduces performance,
75              e.g. by placing two stripes on the same PV.  Optional positional
76              PV args on the command line can also be used to limit which PVs
77              the command will use for allocation.  See lvm(8) for more infor‐
78              mation about allocation.
79
80       -A|--autobackup y|n
81              Specifies if metadata should be backed up automatically after a
82              change.  Enabling this is strongly advised! See vgcfgbackup(8)
83              for more information.
84
85       -c|--clustered y|n
86              Specifies the clustered property of the new VG.
87
88       --commandprofile String
89              The command profile to use for command configuration.  See
90              lvm.conf(5) for more information about profiles.
91
92       --config String
93              Config settings for the command. These override lvm.conf set‐
94              tings.  The String arg uses the same format as lvm.conf, or may
95              use section/field syntax.  See lvm.conf(5) for more information
96              about config.
97
98       -d|--debug ...
99              Set debug level. Repeat from 1 to 6 times to increase the detail
100              of messages sent to the log file and/or syslog (if configured).
101
102       --driverloaded y|n
103              If set to no, the command will not attempt to use device-mapper.
104              For testing and debugging.
105
106       -h|--help
107              Display help text.
108
109       --lockopt String
110              Used to pass options for special cases to lvmlockd.  See lvm‐
111              lockd(8) for more information.
112
113       --longhelp
114              Display long help text.
115
116       -l|--maxlogicalvolumes Number
117              Sets the maximum number of LVs allowed in a VG.
118
119       -p|--maxphysicalvolumes Number
120              Sets the maximum number of PVs that can belong to the VG.  The
121              value 0 removes any limitation.  For large numbers of PVs, also
122              see options --pvmetadatacopies, and --vgmetadatacopies for
123              improving performance.
124
125       -M|--metadatatype lvm2
126              Specifies the type of on-disk metadata to use.  lvm2 (or just 2)
127              is the current, standard format.  lvm1 (or just 1) is no longer
128              used.
129
130       -n|--name String
131              Move only PVs used by the named LV.
132
133       --profile String
134              An alias for --commandprofile or --metadataprofile, depending on
135              the command.
136
137       -q|--quiet ...
138              Suppress output and log messages. Overrides --debug and --ver‐
139              bose.  Repeat once to also suppress any prompts with answer
140              'no'.
141
142       -t|--test
143              Run in test mode. Commands will not update metadata.  This is
144              implemented by disabling all metadata writing but nevertheless
145              returning success to the calling function. This may lead to
146              unusual error messages in multi-stage operations if a tool
147              relies on reading back metadata it believes has changed but
148              hasn't.
149
150       -v|--verbose ...
151              Set verbose level. Repeat from 1 to 4 times to increase the
152              detail of messages sent to stdout and stderr.
153
154       --version
155              Display version information.
156
157       --[vg]metadatacopies all|unmanaged|Number
158              Number of copies of the VG metadata that are kept.  VG metadata
159              is kept in VG metadata areas on PVs in the VG, i.e. reserved
160              space at the start and/or end of the PVs.  Keeping a copy of the
161              VG metadata on every PV can reduce performance in VGs containing
162              a large number of PVs.  When this number is set to a non-zero
163              value, LVM will automatically choose PVs on which to store meta‐
164              data, using the metadataignore flags on PVs to achieve the spec‐
165              ified number.  The number can also be replaced with special
166              string values: unmanaged causes LVM to not automatically manage
167              the PV metadataignore flags.  all causes LVM to first clear the
168              metadataignore flags on all PVs, and then to become unmanaged.
169
170       -y|--yes
171              Do not prompt for confirmation interactively but always assume
172              the answer yes. Use with extreme caution.  (For automatic no,
173              see -qq.)
174

VARIABLES

176       VG
177              Volume Group name.  See lvm(8) for valid names.
178
179       PV
180              Physical Volume name, a device path under  /dev.   For  commands
181              managing physical extents, a PV positional arg generally accepts
182              a suffix indicating a range (or  multiple  ranges)  of  physical
183              extents  (PEs). When the first PE is omitted, it defaults to the
184              start of the device, and when the last PE is omitted it defaults
185              to  end.   Start and end range (inclusive): PV[:PE-PE]...  Start
186              and length range (counting from 0): PV[:PE+PE]...
187
188       String
189              See the option description for information about the string con‐
190              tent.
191
192       Size[UNIT]
193              Size  is  an  input number that accepts an optional unit.  Input
194              units are always treated as base two values, regardless of capi‐
195              talization,  e.g.  'k'  and 'K' both refer to 1024.  The default
196              input unit is specified by letter, followed by |UNIT.  UNIT rep‐
197              resents  other  possible  input units: bBsSkKmMgGtTpPeE.  b|B is
198              bytes, s|S is sectors of 512 bytes, k|K  is  kilobytes,  m|M  is
199              megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes,
200              e|E is exabytes.  (This should not be confused with  the  output
201              control --units, where capital letters mean multiple of 1000.)
202

ENVIRONMENT VARIABLES

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