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}] [-c|--clustered
11 {y|n}] [-d|--debug] [--deltag Tag] [-h|--help] [--ignorelockingfailure]
12 [-l|--logicalvolume MaxLogicalVolumes] [-p|--maxphysicalvolumes Max‐
13 PhysicalVolumes] [-P|--partial] [-s|--physicalextentsize PhysicalEx‐
14 tentSize[kKmMgGtT]] [-t|--test] [-v|--verbose] [--version]
15 [-x|--resizeable {y|n}] [VolumeGroupName...]
16
18 vgchange allows you to change the attributes of one or more volume
19 groups. Its main purpose is to activate and deactivate VolumeGroup‐
20 Name, or all volume groups if none is specified. Only active volume
21 groups are subject to changes and allow access to their logical vol‐
22 umes. [Not yet implemented: During volume group activation, if
23 vgchange recognizes snapshot logical volumes which were dropped because
24 they ran out of space, it displays a message informing the administra‐
25 tor that such snapshots should be removed (see lvremove(8)). ]
26
28 See lvm for common options.
29 -A, --autobackup {y|n}
31 Controls automatic backup of metadata after the change. See
32 vgcfgbackup (8). Default is yes.
33 -a, --available [e|l]{y|n}
35 Controls the availability of the logical volumes in the volume
36 group for input/output. In other words, makes the logical vol‐
37 umes known/unknown to the kernel.
38 If clustered locking is enabled, add 'e' to activate/deactivate
40 exclusively on one node or 'l' to activate/deactivate only on
41 the local node. Logical volumes with single-host snapshots are
42 always activated exclusively because they can only be used on
43 one node at once.
44 -c, --clustered {y|n}
46 If clustered locking is enabled, this indicates whether this
47 Volume Group is shared with other nodes in the cluster or
48 whether it contains only local disks that are not visible on the
49 other nodes. If the cluster infrastructure is unavailable on a
50 particular node at a particular time, you may still be able to
51 use Volume Groups that are not marked as clustered.
52 --monitor {y|n}
54 Controls whether or not a mirrored logical volume is monitored
55 by dmeventd, if it is installed. If a device used by a moni‐
56 tored mirror reports an I/O error, the failure is handled
57 according to mirror_image_fault_policy and mirror_log_fault_pol‐
58 icy set in lvm.conf(5).
59 -l, --logicalvolume MaxLogicalVolumes
61 Changes the maximum logical volume number of an existing inac‐
62 tive volume group.
63 -p, --maxphysicalvolumes MaxPhysicalVolumes
65 Changes the maximum number of physical volumes that can belong
66 to this volume group. For volume groups with metadata in lvm1
67 format, the limit is 255. If the metadata uses lvm2 format, the
68 value 0 removes this restriction: there is then no limit. If
69 you have a large number of physical volumes in a volume group
70 with metadata in lvm2 format, for tool performance reasons, you
71 should consider some use of --metadatacopies 0 as described in
72 pvcreate(8).
73 -s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
75 Changes the physical extent size on physical volumes of this
76 volume group. A size suffix (k for kilobytes up to t for ter‐
77 abytes) is optional, megabytes is the default if no suffix is
78 present. The default is 4 MB and it must be at least 1 KB and a
79 power of 2.
80 Before increasing the physical extent size, you might need to
82 use lvresize, pvresize and/or pvmove so that everything fits.
83 For example, every contiguous range of extents used in a logical
84 volume must start and end on an extent boundary.
85 If the volume group metadata uses lvm1 format, extents can vary
87 in size from 8KB to 16GB and there is a limit of 65534 extents
88 in each logical volume. The default of 4 MB leads to a maximum
89 logical volume size of around 256GB.
90 If the volume group metadata uses lvm2 format those restrictions
92 do not apply, but having a large number of extents will slow
93 down the tools but have no impact on I/O performance to the log‐
94 ical volume. The smallest PE is 1KB.
95 The 2.4 kernel has a limitation of 2TB per block device.
97 -x, --resizeable {y|n}
99 Enables or disables the extension/reduction of this volume group
100 with/by physical volumes.
101
103 To activate all known volume groups in the system:
104 vgchange -a y
106 To change the maximum number of logical volumes of inactive volume
108 group vg00 to 128.
109 vgchange -l 128 /dev/vg00
111
114 lvchange(8), lvm(8), vgcreate(8)
115Sistina Software UK LVM TOOLS VGCHANGE(8)