3 .TH VGCHANGE 8 "LVM TOOLS 2.02.44-cvs (02-17-09)" "Sistina Software UK" \" -*- nroff -*-
5 vgchange \- change attributes of a volume group
11 .IR AllocationPolicy ]
12 .RB [ \-A | \-\-autobackup " {" y | n }]
13 .RB [ \-a | \-\-available " [e|l] {" y | n }]
14 .RB [ \-\-monitor " {" y | n }]
15 .RB [ \-c | \-\-clustered " {" y | n }]
16 .RB [ \-u | \-\-uuid ]
17 .RB [ \-d | \-\-debug]
21 .RB [ \-\-ignorelockingfailure]
22 .RB [ \-\-ignoremonitoring]
23 .RB [ \-l | \-\-logicalvolume
24 .IR MaxLogicalVolumes ]
25 .RB [ -p | \-\-maxphysicalvolumes
26 .IR MaxPhysicalVolumes ]
27 .RB [ \-P | \-\-partial]
28 .RB [ \-s | \-\-physicalextentsize
29 .IR PhysicalExtentSize [ \fBkKmMgGtT\fR ]]
31 .RB [ \-v | \-\-verbose]
33 .RB [ \-x | \-\-resizeable " {" y | n }]
34 .RI [ VolumeGroupName ...]
37 allows you to change the attributes of one or more volume groups.
38 Its main purpose is to activate and deactivate
40 or all volume groups if none is specified. Only active volume groups
41 are subject to changes and allow access to their logical volumes.
42 [Not yet implemented: During volume group activation, if
44 recognizes snapshot logical volumes which were dropped because they ran
45 out of space, it displays a message informing the administrator that such
46 snapshots should be removed (see
50 See \fBlvm\fP for common options.
52 .BR \-A ", " \-\-autobackup " " { y | n }
53 Controls automatic backup of metadata after the change. See
57 .BR \-a ", " \-\-available " " [e|l] { y | n }
58 Controls the availability of the logical volumes in the volume
59 group for input/output.
60 In other words, makes the logical volumes known/unknown to the kernel.
62 If clustered locking is enabled, add 'e' to activate/deactivate
63 exclusively on one node or 'l' to activate/deactivate only
65 Logical volumes with single-host snapshots are always activated
66 exclusively because they can only be used on one node at once.
68 .BR \-c ", " \-\-clustered " " { y | n }
69 If clustered locking is enabled, this indicates whether this
70 Volume Group is shared with other nodes in the cluster or whether
71 it contains only local disks that are not visible on the other nodes.
72 If the cluster infrastructure is unavailable on a particular node at a
73 particular time, you may still be able to use Volume Groups that
74 are not marked as clustered.
77 Generate new random UUID for specified Volume Groups.
79 .BR \-\-monitor " " { y | n }
80 Controls whether or not a mirrored logical volume is monitored by
81 dmeventd, if it is installed.
82 If a device used by a monitored mirror reports an I/O error,
83 the failure is handled according to
84 .BR mirror_image_fault_policy
86 .BR mirror_log_fault_policy
90 .BR \-\-ignoremonitoring
91 Make no attempt to interact with dmeventd unless
94 Do not use this if dmeventd is already monitoring a device.
96 .BR \-l ", " \-\-logicalvolume " " \fIMaxLogicalVolumes\fR
97 Changes the maximum logical volume number of an existing inactive
100 .BR \-p ", " \-\-maxphysicalvolumes " " \fIMaxPhysicalVolumes\fR
101 Changes the maximum number of physical volumes that can belong
102 to this volume group.
103 For volume groups with metadata in lvm1 format, the limit is 255.
104 If the metadata uses lvm2 format, the value 0
105 removes this restriction: there is then no limit.
106 If you have a large number of physical volumes in
107 a volume group with metadata in lvm2 format,
108 for tool performance reasons, you should consider
109 some use of \fB--metadatacopies 0\fP
110 as described in \fBpvcreate(8)\fP.
112 .BR \-s ", " \-\-physicalextentsize " " \fIPhysicalExtentSize\fR[\fBkKmMgGtT\fR]
113 Changes the physical extent size on physical volumes of this volume group.
114 A size suffix (k for kilobytes up to t for terabytes) is optional, megabytes
115 is the default if no suffix is present.
116 The default is 4 MB and it must be at least 1 KB and a power of 2.
118 Before increasing the physical extent size, you might need to use lvresize,
119 pvresize and/or pvmove so that everything fits. For example, every
120 contiguous range of extents used in a logical volume must start and
121 end on an extent boundary.
123 If the volume group metadata uses lvm1 format, extents can vary in size from
124 8KB to 16GB and there is a limit of 65534 extents in each logical volume. The
125 default of 4 MB leads to a maximum logical volume size of around 256GB.
127 If the volume group metadata uses lvm2 format those restrictions do not apply,
128 but having a large number of extents will slow down the tools but have no
129 impact on I/O performance to the logical volume. The smallest PE is 1KB.
131 The 2.4 kernel has a limitation of 2TB per block device.
133 .BR \-x ", " \-\-resizeable " " { y | n }
134 Enables or disables the extension/reduction of this volume group
135 with/by physical volumes.
137 To activate all known volume groups in the system:
143 To change the maximum number of logical volumes of inactive volume group
148 \ vgchange -l 128 /dev/vg00