34
36
.RB [ \-\-noudevsync ]
35
37
.RB [ \-l | \-\-logicalvolume
36
38
.IR MaxLogicalVolumes ]
37
.RB [ -p | \-\-maxphysicalvolumes
39
.RB [ \-p | \-\-maxphysicalvolumes
38
40
.IR MaxPhysicalVolumes ]
41
.RB [ \-\-metadataprofile
39
43
.RB [ \-\- [ vg ] metadatacopies ]
40
44
.IR NumberOfCopies | unmanaged | all ]
41
45
.RB [ \-P | \-\-partial ]
42
46
.RB [ \-s | \-\-physicalextentsize
43
47
.IR PhysicalExtentSize [ bBsSkKmMgGtTpPeE ]]
44
48
.RB [ \-\-refresh ]
49
.RB [ \-t | \-\-test ]
46
50
.RB [ \-v | \-\-verbose ]
47
51
.RB [ \-\-version ]
48
52
.RB [ \-x | \-\-resizeable
81
85
possible to select which volumes to activate using the
82
86
activation/auto_activation_volume_list settting.
88
Activation of a logical volume creates a symbolic link
89
/dev/VolumeGroupName/LogicalVolumeName pointing to the device node.
90
This link is removed on deactivation.
91
All software and scripts should access the device through
92
this symbolic link and present this as the name of the device.
93
The location and name of the underlying device node may depend on
94
the distribution and configuration (e.g. udev) and might change
95
from release to release.
84
97
If clustered locking is enabled, add 'e' to activate/deactivate
85
98
exclusively on one node or 'l' to activate/deactivate only
87
100
Logical volumes with single-host snapshots are always activated
88
101
exclusively because they can only be used on one node at once.
103
.BR \-\-activationmode " {" \fIcomplete | \fIdegraded | \fIpartial }
104
The activation mode determines whether logical volumes are allowed to
105
activate when there are physical volumes missing (e.g. due to a device
106
failure). \fIcomplete is the most restrictive; allowing only those
107
logical volumes to be activated that are not affected by the missing
108
PVs. \fIdegraded allows RAID logical volumes to be activated even if
109
they have PVs missing. (Note that the "mirror" segment type is not
110
considered a RAID logical volume. The "raid1" segment type should
111
be used instead.) Finally, \fIpartial allows any logical volume to
112
be activated even if portions are missing due to a missing or failed
113
PV. This last option should only be used when performing recovery or
114
repair operations. \fIdegraded is the default mode. To change it, modify
90
119
.BR \-K ", " \-\-ignoreactivationskip
91
120
Ignore the flag to skip Logical Volumes during activation.
99
128
are not marked as clustered.
101
130
.BR \-\-detachprofile
102
Detach any configuration profiles attached to given Volume Groups.
103
See also \fBlvm\fP(8) and \fBlvm.conf\fP(5) for more
104
information about configuration profiles.
131
Detach any metadata configuration profiles attached to given
132
Volume Groups. See \fBlvm.conf\fP(5) for more information
133
about \fBmetadata profiles\fP.
106
135
.BR \-u ", " \-\-uuid
107
136
Generate new random UUID for specified Volume Groups.
166
195
If the metadata uses lvm2 format, the value 0 removes this restriction:
167
196
there is then no limit. If you have a large number of physical volumes in
168
197
a volume group with metadata in lvm2 format, for tool performance reasons,
169
you should consider some use of \fB--pvmetadatacopies 0\fP as described in
170
\fBpvcreate(8)\fP, and/or use \fB--vgmetadatacopies\fP.
198
you should consider some use of \fB\-\-pvmetadatacopies 0\fP as described in
199
\fBpvcreate(8)\fP, and/or use \fB\-\-vgmetadatacopies\fP.
201
.BR \-\-metadataprofile " " \fIProfileName
202
Uses and attaches ProfileName configuration profile to the volume group
203
metadata. Whenever the volume group is processed next time, the profile
204
is automatically applied. The profile is inherited by all logical volumes
205
in the volume group unless the logical volume itself has its own profile
206
attached. See \fBlvm.conf\fP(5) for more information about \fBmetadata profiles\fP.
172
208
.BR \-\- [ vg ] metadatacopies " " \fINumberOfCopies | \fIunmanaged | \fIall
173
209
Sets the desired number of metadata copies in the volume group. If set to
174
210
a non-zero value, LVM will automatically manage the 'metadataignore'
175
flags on the physical volumes (see \fBpvchange\fP or \fBpvcreate --metadataignore\fP) in order
211
flags on the physical volumes (see \fBpvchange\fP or \fBpvcreate \-\-metadataignore\fP) in order
176
212
to achieve \fINumberOfCopies\fP copies of metadata. If set to \fIunmanaged\fP,
177
213
LVM will not automatically manage the 'metadataignore' flags. If set to
178
214
\fIall\fP, LVM will first clear all of the 'metadataignore' flags on all
added
removed
man/vgchange.8.in
