1VGCHANGE(8) System Manager's Manual VGCHANGE(8)
2
6 vgchange - change attributes of a volume group
7
9 vgchange [--addtag Tag] [--alloc AllocationPolicy] [-A|--autobackup
10 {y|n}] [-a|--available [e|l] {y|n}] [--monitor {y|n}] [--poll {y|n}]
11 [-c|--clustered {y|n}] [-u|--uuid] [-d|--debug] [--deltag Tag]
12 [-h|--help] [--ignorelockingfailure] [--ignoremonitoring] [--sysinit]
13 [--noudevsync] [-l|--logicalvolume MaxLogicalVolumes] [-p|--maxphysi‐
14 calvolumes MaxPhysicalVolumes] [--[vg]metadatacopies] NumberOf‐
15 Copies|unmanaged|all] [-P|--partial] [-s|--physicalextentsize Physi‐
16 calExtentSize[bBsSkKmMgGtTpPeE]] [--refresh] [-t|--test] [-v|--verbose]
17 [--version] [-x|--resizeable {y|n}] [VolumeGroupName...]
18
20 vgchange allows you to change the attributes of one or more volume
21 groups. Its main purpose is to activate and deactivate VolumeGroup‐
22 Name, or all volume groups if none is specified. Only active volume
23 groups are subject to changes and allow access to their logical vol‐
24 umes. [Not yet implemented: During volume group activation, if
25 vgchange recognizes snapshot logical volumes which were dropped because
26 they ran out of space, it displays a message informing the administra‐
27 tor that such snapshots should be removed (see lvremove(8)). ]
28
30 See lvm for common options.
31 -A, --autobackup {y|n}
33 Controls automatic backup of metadata after the change. See
34 vgcfgbackup (8). Default is yes.
35 -a, --available [e|l]{y|n}
37 Controls the availability of the logical volumes in the volume
38 group for input/output. In other words, makes the logical vol‐
39 umes known/unknown to the kernel.
40 If clustered locking is enabled, add 'e' to activate/deactivate
42 exclusively on one node or 'l' to activate/deactivate only on
43 the local node. Logical volumes with single-host snapshots are
44 always activated exclusively because they can only be used on
45 one node at once.
46 -c, --clustered {y|n}
48 If clustered locking is enabled, this indicates whether this
49 Volume Group is shared with other nodes in the cluster or
50 whether it contains only local disks that are not visible on the
51 other nodes. If the cluster infrastructure is unavailable on a
52 particular node at a particular time, you may still be able to
53 use Volume Groups that are not marked as clustered.
54 -u, --uuid
56 Generate new random UUID for specified Volume Groups.
57 --monitor {y|n}
59 Start or stop monitoring a mirrored or snapshot logical volume
60 with dmeventd, if it is installed. If a device used by a moni‐
61 tored mirror reports an I/O error, the failure is handled
62 according to mirror_image_fault_policy and mirror_log_fault_pol‐
63 icy set in lvm.conf(5).
64 --poll {y|n}
66 Without polling a logical volume's backgrounded transformation
67 process will never complete. If there is an incomplete pvmove
68 or lvconvert (for example, on rebooting after a crash), use
69 --poll y to restart the process from its last checkpoint. How‐
70 ever, it may not be appropriate to immediately poll a logical
71 volume when it is activated, use --poll n to defer and then
72 --poll y to restart the process.
73 --sysinit
75 Indicates that vgchange(8) is being invoked from early system
76 initialisation scripts (e.g. rc.sysinit or an initrd), before
77 writeable filesystems are available. As such, some functionality
78 needs to be disabled and this option acts as a shortcut which
79 selects an appropriate set of options. Currently this is equiva‐
80 lent to using --ignorelockingfailure, --ignoremonitoring,
81 --poll n and setting LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES envi‐
82 ronment variable.
83 --noudevsync
85 Disable udev synchronisation. The process will not wait for
86 notification from udev. It will continue irrespective of any
87 possible udev processing in the background. You should only use
88 this if udev is not running or has rules that ignore the devices
89 LVM2 creates.
90 --ignoremonitoring
92 Make no attempt to interact with dmeventd unless --monitor is
93 specified. Do not use this if dmeventd is already monitoring a
94 device.
95 -l, --logicalvolume MaxLogicalVolumes
97 Changes the maximum logical volume number of an existing inac‐
98 tive volume group.
99 -p, --maxphysicalvolumes MaxPhysicalVolumes
101 Changes the maximum number of physical volumes that can belong
102 to this volume group. For volume groups with metadata in lvm1
103 format, the limit is 255. If the metadata uses lvm2 format, the
104 value 0 removes this restriction: there is then no limit. If
105 you have a large number of physical volumes in a volume group
106 with metadata in lvm2 format, for tool performance reasons, you
107 should consider some use of --pvmetadatacopies 0 as described in
108 pvcreate(8), and/or use --vgmetadatacopies.
109 --[vg]metadatacopies NumberOfCopies|unmanaged|all
111 Sets the desired number of metadata copies in the volume group.
112 If set to a non-zero value, LVM will automatically manage the
113 'metadataignore' flags on the physical volumes (see pvchange or
114 pvcreate --metadataignore) in order to achieve NumberOfCopies
115 copies of metadata. If set to unmanaged, LVM will not automati‐
116 cally manage the 'metadataignore' flags. If set to all, LVM
117 will first clear all of the 'metadataignore' flags on all meta‐
118 data areas in the volume group, then set the value to unmanaged.
119 The vgmetadatacopies option is useful for volume groups contain‐
120 ing large numbers of physical volumes with metadata as it may be
121 used to minimize metadata read and write overhead.
122 -s, --physicalextentsize PhysicalExtentSize[bBsSkKmMgGtTpPeE]
124 Changes the physical extent size on physical volumes of this
125 volume group. A size suffix (k for kilobytes up to t for ter‐
126 abytes) is optional, megabytes is the default if no suffix is
127 present. The default is 4 MB and it must be at least 1 KB and a
128 power of 2.
129 Before increasing the physical extent size, you might need to
131 use lvresize, pvresize and/or pvmove so that everything fits.
132 For example, every contiguous range of extents used in a logical
133 volume must start and end on an extent boundary.
134 If the volume group metadata uses lvm1 format, extents can vary
136 in size from 8KB to 16GB and there is a limit of 65534 extents
137 in each logical volume. The default of 4 MB leads to a maximum
138 logical volume size of around 256GB.
139 If the volume group metadata uses lvm2 format those restrictions
141 do not apply, but having a large number of extents will slow
142 down the tools but have no impact on I/O performance to the log‐
143 ical volume. The smallest PE is 1KB.
144 The 2.4 kernel has a limitation of 2TB per block device.
146 --refresh
148 If any logical volume in the volume group is active, reload its
149 metadata. This is not necessary in normal operation, but may be
150 useful if something has gone wrong or if you're doing clustering
151 manually without a clustered lock manager.
152 -x, --resizeable {y|n}
154 Enables or disables the extension/reduction of this volume group
155 with/by physical volumes.
156
158 To activate all known volume groups in the system:
159 vgchange -a y
161 To change the maximum number of logical volumes of inactive volume
163 group vg00 to 128.
164 vgchange -l 128 /dev/vg00
166
169 lvchange(8), lvm(8), vgcreate(8)
170Sistina Software UK LVM TOOLS 2.02.84(2) (2011-02-09) VGCHANGE(8)