Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vgsplit(8) [redhat man page]

VGSPLIT(8)						      System Manager's Manual							VGSPLIT(8)

NAME
vgsplit - split a volume groups SYNOPSIS
vgsplit [-A|--autobackup {y|n}] [-d|-ebug] [-h|--help] [-l|--list] [-t|--test] [-v|--verbose] [--version] ExistingVolumeGroupName NewVol- umeGroupName PhysicalVolumePath [PhysicalVolumePath...] DESCRIPTION
vgsplit moves one or more PhysicalVolumePath(s) from ExistingVolumeGroupName into NewVolumeGroupName. Physical volumes that are split off to the new volume group must not contain any partial logical volumes. Use pvmove(8) to move logical volumes to the desired physical vol- umes. OPTIONS -A, --autobackup {y|n} Controls automatic backup of VG metadata after the merge (see vgcfgbackup(8)). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -l, --list Display split volume group names like vgdisplay -v. -t, --test Do a test run WITHOUT any real changes. -v, --verbose Display verbose runtime information about vgsplit's activities. --version Display tool and IOP version and exit successfully. EXAMPLE
To separate physical volumes /dev/sdk1 and /dev/sdn1 from the existing volume group databases and put them into new volume group my_vg. vgsplit -v databases my_vg /dev/sdk1 /dev/sdn1 DIAGNOSTICS
vgsplit returns an exit code of 0 for success and > 0 for error: 1 invalid volume group name 2 invalid physical volume name 3 malloc error 4 error reading VGDA of existing volume group 5 new volume group already exists 6 error setting up VGDA for split 7 logical volume to be split into new volume group must be inactive 8 logical volume doesn't exist 9 error removing logical volume from kernel 10 error reducing VGDA by physical volume in kernel 11 error writing changed existing VGDA to physical volume(s) 12 error writing new VGDA to physical volume(s) 13 error creating device special files for changed existing volume group 14 error creating device special files for new volume group 15 error creating new VGDA in kernel 16 error inserting new volume group name into lvmtab 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line ENVIRONMENT VARIABLES
LVM_AUTOBACKUP If this variable is set to "no" then the automatic backup of VG metadata is turned off. LVM_VG_MAX_BACKUPS This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number between 0 and 999. The higher this number is, the more changes you can restore using vgcfgrestore(8). SEE ALSO
lvm(8), vgcreate(8), vgextend(8), vgreduce(8), vgmerge(8), pvmove(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGSPLIT(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)
Man Page