vgextend(8) [redhat man page]

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

NAME

       vgextend - add physical volumes to a volume group

SYNOPSIS

       vgextend [-A|--autobackup{y|n}] [-d|--debug] [-h|--help] [-v|--verbose] VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]

DESCRIPTION

       vgextend allows you to add one or more initialized physical volumes ( see pvcreate(8) ) to an existing volume group to extend it in size.

   OPTIONS
       -A, --autobackup y/n
	      Controls automatic backup of VG metadata after the change ( 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.

       -v, --verbose
	      Gives verbose runtime information about lvextend's activities.

Examples
       "vgextend  vg00	/dev/sda4  /dev/sdn1"  tries  to  extend  the  existing volume group "vg00" by the new physical volumes (see pvcreate(8) )
       "/dev/sdn1" and /dev/sda4".

DIAGNOSTICS

       vgextend returns an exit code of 0 for success and > 0 for error:

       1  no volume group name on command line
       2  volume group name not given as first argument
       3  no physical volume(s) on command line
       4  invalid volume group name
       5  error checking existence of volume group
       6  inactive volume group
       7  error reading VGDA
       8  volume group is set to not extendable
       9  maximum physical volume number of volume group exceeded
       10 error reading all physical volumes
       11 error setting up VGDA
       12 error extending VGDA in kernel
       13 error writing VGDA to physical volume(s)

       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), vgreduce(8), pvcreate(8)

AUTHOR

       Heinz Mauelshagen <Linux-LVM@Sistina.com>

Heinz Mauelshagen						     LVM TOOLS							       VGEXTEND(8)

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

NAME

       vgmerge - merge two volume groups

SYNOPSIS

       vgmerge	[-A|--autobackup{y|n}]	[-d|--debug]  [-h|--help]  [-l|--list]	[-t|--test]  [-v|--verbose]  DestinationVolumeGroupName SourceVol-
       umeGroupName

DESCRIPTION

       vgmerge merges two existing volume groups. The inactive SourceVolumeGroupName will be merged into the DestinationVolumeGroupName if  physi-
       cal extent sizes are equal and physical and logical volume summaries of both volume groups fit into DestinationVolumeGroupName's limits.

   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 merged DestinationVolumeGroupName like "vgdisplay -v".

       -t, --test
	      Do a test run WITHOUT making any real changes.

       -v, --verbose
	      Display verbose runtime information about vgmerge's activities.

Examples
       "vgmerge -v databases my_vg" merges the inactive volume group named "my_vg" into the active or inactive volume group named "databases" giv-
       ing verbose runtime information.

DIAGNOSTICS

       vgmerge returns an exit code of 0 for success and > 0 for error:

       1  2 volume group names must be entered on command line
       2  volume group to merge from must be inactive
       3  error reading VGDA of volume group to merge into
       4  error reading VGDA of volume group to merge from
       5  error setting up VGDA for merge
       6  error extending VGDA by physical volume in kernel
       7  error writing VGDA to physical volume(s)
       8  error creating volume group special files
       9  error removing volume group from 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 also1
       lvm(8), vgcreate(8), vgextend(8), vgreduce(8), vgsplit(8), pvmove(8)

AUTHOR

       Heinz Mauelshagen <Linux-LVM@Sistina.com>

Heinz Mauelshagen						     LVM TOOLS								VGMERGE(8)