pvscan(8) [centos man page]
PVSCAN(8) System Manager's Manual PVSCAN(8) NAME
pvscan - scan all disks for physical volumes SYNOPSIS
pvscan [-d|--debug] [-h|--help] [-v|--verbose] [--version] [--ignorelockingfailure] [-e|--exported] [-n|--novolumegroup] [-s|--short] [-u|--uuid] pvscan [-d|--debug] [-h|--help] --cache [-a|--activate ay] [-b|--background] [--major major --minor minor | DevicePath | major:minor]... DESCRIPTION
pvscan scans all supported LVM block devices in the system for physical volumes. OPTIONS
See lvm(8) for common options. -e, --exported Only show physical volumes belonging to exported volume groups. -n, --novolumegroup Only show physical volumes not belonging to any volume group. -s, --short Short listing format. -u, --uuid Show UUIDs (Uniform Unique Identifiers) in addition to device special names. -a, --activate ay Together with the information already cached in lvmetad, automatically activate any logical volumes that become activatable after the scan done on one or more devices. The logical volume to autoactivate is matched against the activation/auto_activation_vol- ume_list set in lvm.conf. If this list is not set, then all volumes are considered for autoactivation. The autoactivation is not yet supported for logical volumes that are part of partial or clustered volume groups. -b, --background Run the command in the background. --cache [--major major --minor minor | DevicePath | major:minor ]... Scan one or more devices and instruct the lvmetad daemon to update its cached state accordingly. Called internally by udev rules. All devices listed explicitly are processed regardless of any device filters set using devices/filter configuration setting. To fil- ter devices even in this case, the devices/global_filter must be used. If lvmetad has not yet cached any metadata or the filters have recently been changed, then all devices may be scanned, effectively ignoring the rest of the command line. Otherwise, if all the devices referenced on the command line contain metadata in the default lvm2 format, other devices are not accessed. If metadata written using the obsolete GFS pool format is encountered, this is ignored and so lvmetad should not be used. SEE ALSO
lvm(8), lvmetad(8), pvcreate(8), pvdisplay(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) PVSCAN(8)
Check Out this Related Man Page
VGSPLIT(8) System Manager's Manual VGSPLIT(8) NAME
vgsplit - split a volume group into two SYNOPSIS
vgsplit [--alloc AllocationPolicy] [-A|--autobackup {y|n}] [-c|--clustered {y|n}] [-d|--debug] [-h|--help] [-l|--maxlogicalvolumes MaxLogi- calVolumes] [-M|--metadatatype type] [-p|--maxphysicalvolumes MaxPhysicalVolumes] [--[vg]metadatacopies NumberOfCopies|unmanaged|all] [-n|--name LogicalVolumeName] [-t|--test] [-v|--verbose] SourceVolumeGroupName DestinationVolumeGroupName [PhysicalVolumePath...] DESCRIPTION
vgsplit moves one or more physical volumes from SourceVolumeGroupName into DestinationVolumeGroupName. The physical volumes moved can be specified either explicitly via PhysicalVolumePath, or implicitly by -n LogicalVolumeName, in which case only physical volumes underlying the specified logical volume will be moved. If DestinationVolumeGroupName does not exist, a new volume group will be created. The default attributes for the new volume group can be specified with --alloc, --clustered, --maxlogicalvolumes, --metadatatype, --maxphysicalvolumes and --[vg]metadatacopies (see vgcreate(8) for a description of these options). If any of these options are not given, default attribute(s) are taken from SourceVolumeGroupName. If a non-LVM2 metadata type (e.g. lvm1) is being used, you should use the -M option to specify the metadata type directly. If DestinationVolumeGroupName does exist, it will be checked for compatibility with SourceVolumeGroupName before the physical volumes are moved. Specifying any of the above default volume group attributes with an existing destination volume group is an error, and no split will occur. Logical volumes cannot be split between volume groups. vgsplit(8) only moves complete physical volumes: To move part of a physical volume, use pvmove(8). Each existing logical volume must be entirely on the physical volumes forming either the source or the destination volume group. For this reason, vgsplit(8) may fail with an error if a split would result in a logical volume being split across volume groups. A vgsplit into an existing volume group retains the existing volume group's value of vgmetadatacopies (see vgcreate(8) and lvm.conf(5) for further explanation of vgmetadatacopies). To change the value of vgmetadatacopies, use vgchange(8). OPTIONS
See lvm(8) for common options. SEE ALSO
lvm(8), vgcreate(8), vgextend(8), vgreduce(8), vgmerge(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) VGSPLIT(8)