lvmdump(8) [centos man page]
LVMDUMP(8) System Manager's Manual LVMDUMP(8) NAME
lvmdump - create lvm2 information dumps for diagnostic purposes SYNOPSIS
lvmdump [-a] [-c] [-d directory] [-h] [-l] [-m] [-u] DESCRIPTION
lvmdump is a tool to dump various information concerning LVM2. By default, it creates a tarball suitable for submission along with a prob- lem report. The content of the tarball is as follows: - dmsetup info - table of currently running processes - recent entries from /var/log/messages (containing system messages) - complete lvm configuration and cache (content of /etc/lvm) - list of device nodes present under /dev - list of files present /sys/block - list of files present /sys/devices/virtual/block - if enabled with -m, metadata dump will be also included - if enabled with -a, debug output of vgscan, pvscan and list of all available volume groups, physical volumes and logical volumes will be included - if enabled with -c, cluster status info - if enabled with -l, lvmetad state if running - if enabled with -u, udev info and context OPTIONS
-a Advanced collection. WARNING: if lvm is already hung, then this script may hang as well if -a is used. -c If clvmd is running, gather cluster data as well. -d directory Dump into a directory instead of tarball By default, lvmdump will produce a single compressed tarball containing all the informa- tion. Using this option, it can be instructed to only produce the raw dump tree, rooted in directory. -h Print help message -l Include lvmetad(8) daemon dump if it is running. The dump contains cached information that is currently stored in lvmetad: VG meta- data, PV metadata and various mappings in between these metadata for quick access. -m Gather LVM metadata from the PVs This option generates a 1:1 dump of the metadata area from all PVs visible to the system, which can cause the dump to increase in size considerably. However, the metadata dump may represent a valuable diagnostic resource. -u Gather udev info and context: /etc/udev/udev.conf file, udev daemon version (output of 'udevadm info --version' command), udev rules currently used in the system (content of /lib/udev/rules.d and /etc/udev/rules.d directory), list of files in /lib/udev directory and dump of current udev database content (the output of 'udevadm info --export-db' command). ENVIRONMENT VARIABLES
LVM_BINARY The LVM2 binary to use. Defaults to "lvm". Sometimes you might need to set this to "/sbin/lvm.static", for example. DMSETUP_BINARY The dmsetup binary to use. Defaults to "dmsetup". SEE ALSO
lvm(8) Red Hat, Inc. LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVMDUMP(8)
Check Out this Related Man Page
VGCHANGE(8) System Manager's Manual VGCHANGE(8) NAME
vgchange - change attributes of a volume group SYNOPSIS
vgchange [--addtag Tag] [--alloc AllocationPolicy] [-A|--autobackup {y|n}] [-a|--activate [a|e|l] {y|n}] [-K|--ignoreactivationskip] [--monitor {y|n}] [--poll {y|n}] [-c|--clustered {y|n}] [-u|--uuid] [-d|--debug] [--deltag Tag] [--profile ProfileName] [--detachprofile] [-h|--help] [--ignorelockingfailure] [--ignoremonitoring] [--ignoreskippedcluster] [--sysinit] [--noudevsync] [-l|--logicalvolume MaxLogi- calVolumes] [-p|--maxphysicalvolumes MaxPhysicalVolumes] [--[vg]metadatacopies] NumberOfCopies|unmanaged|all] [-P|--partial] [-s|--physi- calextentsize PhysicalExtentSize[bBsSkKmMgGtTpPeE]] [--refresh] [-t|--test] [-v|--verbose] [--version] [-x|--resizeable {y|n}] [Vol- umeGroupName...] DESCRIPTION
vgchange allows you to change the attributes of one or more volume groups. Its main purpose is to activate and deactivate VolumeGroupName, or all volume groups if none is specified. Only active volume groups are subject to changes and allow access to their logical volumes. [Not yet implemented: During volume group activation, if vgchange recognizes snapshot logical volumes which were dropped because they ran out of space, it displays a message informing the administrator that such snapshots should be removed (see lvremove(8)). ] OPTIONS
See lvm(8) for common options. -A, --autobackup {y|n} Controls automatic backup of metadata after the change. See vgcfgbackup(8). Default is yes. -a, --activate [a|e|l]{y|n} Controls the availability of the logical volumes in the volume group for input/output. In other words, makes the logical volumes known/unknown to the kernel. If autoactivation option is used (-aay), each logical volume in the volume group is activated only if it matches an item in the activation/auto_activation_volume_list set in lvm.conf. If this list is not set, then all volumes are con- sidered for activation. The -aay option should be also used during system boot so it's possible to select which volumes to activate using the activation/auto_activation_volume_list settting. If clustered locking is enabled, add 'e' to activate/deactivate exclusively on one node or 'l' to activate/deactivate only on the local node. Logical volumes with single-host snapshots are always activated exclusively because they can only be used on one node at once. -K, --ignoreactivationskip Ignore the flag to skip Logical Volumes during activation. -c, --clustered {y|n} If clustered locking is enabled, this indicates whether this Volume Group is shared with other nodes in the cluster or whether it contains only local disks that are not visible on the other nodes. If the cluster infrastructure is unavailable on a particular node at a particular time, you may still be able to use Volume Groups that are not marked as clustered. --detachprofile Detach any configuration profiles attached to given Volume Groups. See also lvm(8) and lvm.conf(5) for more information about con- figuration profiles. -u, --uuid Generate new random UUID for specified Volume Groups. --monitor {y|n} Start or stop monitoring a mirrored or snapshot logical volume with dmeventd, if it is installed. If a device used by a monitored mirror reports an I/O error, the failure is handled according to mirror_image_fault_policy and mirror_log_fault_policy set in lvm.conf(5). --poll {y|n} Without polling a logical volume's backgrounded transformation process will never complete. If there is an incomplete pvmove or lvconvert (for example, on rebooting after a crash), use --poll y to restart the process from its last checkpoint. However, it may not be appropriate to immediately poll a logical volume when it is activated, use --poll n to defer and then --poll y to restart the process. --sysinit Indicates that vgchange(8) is being invoked from early system initialisation scripts (e.g. rc.sysinit or an initrd), before write- able filesystems are available. As such, some functionality needs to be disabled and this option acts as a shortcut which selects an appropriate set of options. Currently this is equivalent to using --ignorelockingfailure, --ignoremonitoring, --poll n and setting LVM_SUPPRESS_LOCKING_FAILURE_MESSAGES environment variable. If --sysinit is used in conjunction with lvmetad(8) enabled and running, autoactivation is preferred over manual activation via direct vgchange call. Logical volumes are autoactivated according to auto_activation_volume_list set in lvm.conf(5). --noudevsync Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 cre- ates. --ignoremonitoring Make no attempt to interact with dmeventd unless --monitor is specified. Do not use this if dmeventd is already monitoring a device. -l, --logicalvolume MaxLogicalVolumes Changes the maximum logical volume number of an existing inactive volume group. -p, --maxphysicalvolumes MaxPhysicalVolumes Changes the maximum number of physical volumes that can belong to this volume group. For volume groups with metadata in lvm1 for- mat, the limit is 255. If the metadata uses lvm2 format, the value 0 removes this restriction: there is then no limit. If you have a large number of physical volumes in a volume group with metadata in lvm2 format, for tool performance reasons, you should consider some use of --pvmetadatacopies 0 as described in pvcreate(8), and/or use --vgmetadatacopies. --[vg]metadatacopies NumberOfCopies|unmanaged|all Sets the desired number of metadata copies in the volume group. If set to a non-zero value, LVM will automatically manage the 'metadataignore' flags on the physical volumes (see pvchange or pvcreate --metadataignore) in order to achieve NumberOfCopies copies of metadata. If set to unmanaged, LVM will not automatically manage the 'metadataignore' flags. If set to all, LVM will first clear all of the 'metadataignore' flags on all metadata areas in the volume group, then set the value to unmanaged. The vgmetadata- copies option is useful for volume groups containing large numbers of physical volumes with metadata as it may be used to minimize metadata read and write overhead. -s, --physicalextentsize PhysicalExtentSize[BbBsSkKmMgGtTpPeE] Changes the physical extent size on physical volumes of this volume group. A size suffix (k for kilobytes up to t for terabytes) is optional, megabytes is the default if no suffix is present. The value must be at least 1 sector for LVM2 format (where the sector size is the largest sector size of the PVs currently used in the VG) or 8KiB for LVM1 format and it must be a power of 2. The default is 4 MiB. Before increasing the physical extent size, you might need to use lvresize, pvresize and/or pvmove so that everything fits. For example, every contiguous range of extents used in a logical volume must start and end on an extent boundary. If the volume group metadata uses lvm1 format, extents can vary in size from 8KiB to 16GiB and there is a limit of 65534 extents in each logical volume. The default of 4 MiB leads to a maximum logical volume size of around 256GiB. If the volume group metadata uses lvm2 format those restrictions do not apply, but having a large number of extents will slow down the tools but have no impact on I/O performance to the logical volume. The smallest PE is 1KiB. The 2.4 kernel has a limitation of 2TiB per block device. --refresh If any logical volume in the volume group is active, reload its metadata. This is not necessary in normal operation, but may be useful if something has gone wrong or if you're doing clustering manually without a clustered lock manager. -x, --resizeable {y|n} Enables or disables the extension/reduction of this volume group with/by physical volumes. Examples To activate all known volume groups in the system: vgchange -a y To change the maximum number of logical volumes of inactive volume group vg00 to 128. vgchange -l 128 /dev/vg00 SEE ALSO
lvchange(8), lvm(8), vgcreate(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) VGCHANGE(8)