1 .TH VGCHANGE 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
3 vgchange \- change attributes of a volume group
10 .RB [ \-A | \-\-autobackup
12 .RB [ \-a | \-\-available
19 .RB [ \-c | \-\-clustered
21 .RB [ \-u | \-\-uuid ]
22 .RB [ \-d | \-\-debug ]
25 .RB [ \-h | \-\-help ]
26 .RB [ \-\-ignorelockingfailure ]
27 .RB [ \-\-ignoremonitoring ]
29 .RB [ \-\-noudevsync ]
30 .RB [ \-l | \-\-logicalvolume
31 .IR MaxLogicalVolumes ]
32 .RB [ -p | \-\-maxphysicalvolumes
33 .IR MaxPhysicalVolumes ]
34 .RB [ \-\- [ vg ] metadatacopies ]
35 .IR NumberOfCopies | unmanaged | all ]
36 .RB [ \-P | \-\-partial ]
37 .RB [ \-s | \-\-physicalextentsize
38 .IR PhysicalExtentSize [ bBsSkKmMgGtTpPeE ]]
41 .RB [ \-v | \-\-verbose ]
43 .RB [ \-x | \-\-resizeable
45 .RI [ VolumeGroupName ...]
47 vgchange allows you to change the attributes of one or more
48 volume groups. Its main purpose is to activate and deactivate
50 or all volume groups if none is specified. Only active volume groups
51 are subject to changes and allow access to their logical volumes.
52 [Not yet implemented: During volume group activation, if
54 recognizes snapshot logical volumes which were dropped because they ran
55 out of space, it displays a message informing the administrator that such
56 snapshots should be removed (see
60 See \fBlvm\fP(8) for common options.
62 .BR \-A ", " \-\-autobackup " {" \fIy | \fIn }
63 Controls automatic backup of metadata after the change. See
67 .BR \-a ", " \-\-available " [" \fIe | \fIl ]{ \fIy | \fIn }
68 Controls the availability of the logical volumes in the volume
69 group for input/output.
70 In other words, makes the logical volumes known/unknown to the kernel.
72 If clustered locking is enabled, add 'e' to activate/deactivate
73 exclusively on one node or 'l' to activate/deactivate only
75 Logical volumes with single-host snapshots are always activated
76 exclusively because they can only be used on one node at once.
78 .BR \-c ", " \-\-clustered " {" \fIy | \fIn }
79 If clustered locking is enabled, this indicates whether this
80 Volume Group is shared with other nodes in the cluster or whether
81 it contains only local disks that are not visible on the other nodes.
82 If the cluster infrastructure is unavailable on a particular node at a
83 particular time, you may still be able to use Volume Groups that
84 are not marked as clustered.
87 Generate new random UUID for specified Volume Groups.
89 .BR \-\-monitor " {" \fIy | \fIn }
90 Start or stop monitoring a mirrored or snapshot logical volume with
91 dmeventd, if it is installed.
92 If a device used by a monitored mirror reports an I/O error,
93 the failure is handled according to
94 .B mirror_image_fault_policy
96 .B mirror_log_fault_policy
100 .BR \-\-poll " {" \fIy | \fIn }
101 Without polling a logical volume's backgrounded transformation process
102 will never complete. If there is an incomplete pvmove or lvconvert (for
103 example, on rebooting after a crash), use \fB\-\-poll y\fP to restart the
104 process from its last checkpoint. However, it may not be appropriate to
105 immediately poll a logical volume when it is activated, use
106 \fB\-\-poll n\fP to defer and then \fB\-\-poll y\fP to restart the process.
109 Indicates that vgchange(8) is being invoked from early system initialisation
110 scripts (e.g. rc.sysinit or an initrd), before writeable filesystems are
111 available. As such, some functionality needs to be disabled and this option
112 acts as a shortcut which selects an appropriate set of options. Currently
113 this is equivalent to using
114 .BR \-\-ignorelockingfailure ,
115 .BR \-\-ignoremonitoring ,
117 and setting \fBLVM_SUPPRESS_LOCKING_FAILURE_MESSAGES\fP
118 environment variable.
121 Disable udev synchronisation. The
122 process will not wait for notification from udev.
123 It will continue irrespective of any possible udev processing
124 in the background. You should only use this if udev is not running
125 or has rules that ignore the devices LVM2 creates.
127 .BR \-\-ignoremonitoring
128 Make no attempt to interact with dmeventd unless
131 Do not use this if dmeventd is already monitoring a device.
133 .BR \-l ", " \-\-logicalvolume " " \fIMaxLogicalVolumes
134 Changes the maximum logical volume number of an existing inactive
137 .BR \-p ", " \-\-maxphysicalvolumes " " \fIMaxPhysicalVolumes
138 Changes the maximum number of physical volumes that can belong
139 to this volume group.
140 For volume groups with metadata in lvm1 format, the limit is 255.
141 If the metadata uses lvm2 format, the value 0 removes this restriction:
142 there is then no limit. If you have a large number of physical volumes in
143 a volume group with metadata in lvm2 format, for tool performance reasons,
144 you should consider some use of \fB--pvmetadatacopies 0\fP as described in
145 \fBpvcreate(8)\fP, and/or use \fB--vgmetadatacopies\fP.
147 .BR \-\- [ vg ] metadatacopies " " \fINumberOfCopies | \fIunmanaged | \fIall
148 Sets the desired number of metadata copies in the volume group. If set to
149 a non-zero value, LVM will automatically manage the 'metadataignore'
150 flags on the physical volumes (see \fBpvchange\fP or \fBpvcreate --metadataignore\fP) in order
151 to achieve \fINumberOfCopies\fP copies of metadata. If set to \fIunmanaged\fP,
152 LVM will not automatically manage the 'metadataignore' flags. If set to
153 \fIall\fP, LVM will first clear all of the 'metadataignore' flags on all
154 metadata areas in the volume group, then set the value to \fIunmanaged\fP.
155 The \fBvgmetadatacopies\fP option is useful for volume groups containing
156 large numbers of physical volumes with metadata as it may be used to
157 minimize metadata read and write overhead.
159 .BR \-s ", " \-\-physicalextentsize " " \fIPhysicalExtentSize [ \fIBbBsSkKmMgGtTpPeE ]
160 Changes the physical extent size on physical volumes of this volume group.
161 A size suffix (k for kilobytes up to t for terabytes) is optional, megabytes
162 is the default if no suffix is present.
163 The default is 4 MiB and it must be at least 1 KiB and a power of 2.
165 Before increasing the physical extent size, you might need to use lvresize,
166 pvresize and/or pvmove so that everything fits. For example, every
167 contiguous range of extents used in a logical volume must start and
168 end on an extent boundary.
170 If the volume group metadata uses lvm1 format, extents can vary in size from
171 8KiB to 16GiB and there is a limit of 65534 extents in each logical volume.
172 The default of 4 MiB leads to a maximum logical volume size of around 256GiB.
174 If the volume group metadata uses lvm2 format those restrictions do not apply,
175 but having a large number of extents will slow down the tools but have no
176 impact on I/O performance to the logical volume. The smallest PE is 1KiB.
178 The 2.4 kernel has a limitation of 2TiB per block device.
181 If any logical volume in the volume group is active, reload its metadata.
182 This is not necessary in normal operation, but may be useful
183 if something has gone wrong or if you're doing clustering
184 manually without a clustered lock manager.
186 .BR \-x ", " \-\-resizeable " {" \fIy | \fIn }
187 Enables or disables the extension/reduction of this volume group
188 with/by physical volumes.
190 To activate all known volume groups in the system:
194 To change the maximum number of logical volumes of inactive volume group
197 .B vgchange -l 128 /dev/vg00
git://sourceware.org / lvm2.git / blob