vgmerge(8) [redhat man page]

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)

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

NAME

       lvrename - rename a logical volume

SYNOPSIS

       lvrename [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-v|--verbose] [--version]

       {OldLogicalVolumePath NewLogicalVolume{Path|Name} |

       VolumeGroupName OldLogicalVolumeName NewLogicalVolumeName}

DESCRIPTION

       lvrename renames an existing logical volume from OldLogicalVolume{Name|Path} to NewLogicalVolume{Name|Path}.

   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 progress messages.

EXAMPLE

       To rename lvold in volume group vg02 to lvnew:

	    lvrename /dev/vg02/lvold /dev/vg02/lvnew

       An alternate syntax to rename this logical volume is

	    lvrename vg02 lvold lvnew

DIAGNOSTICS

       lvrename returns an exit code of 0 for success or > 0 for error:

       1  invalid logical volume name
       2  error checking existence of volume group
       3  volume group inactive
       4  new logical volume special file already exists
       5  old logical volume doesn't exist
       6  volume group names are different
       7  new logical volume already exist
       9  error reading volume group
       10 error getting index of old logical volume
       11 error renaming logical volume in kernel
       12 error creating new logical volume in kernel
       13 error writing VGDA to physical volume(s)
       14 error creating device special for new logical volume
       15 invalid volume group name

       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  determins  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 steps are you able to backup with vgcfgrestore(8) from the changes  you  make
	      to your volume groups.

       LVM_VG_NAME
	      The  default  Volume Group Name to use. Setting this variable enables you to enter just the Logical Volume Name rather than its com-
	      plete path.

SEE ALSO

       lvm(8), lvchange(8), vgcreate(8), vgrename(8)

AUTHOR

       Heinz Mauelshagen <Linux-LVM@Sistina.com>

Heinz Mauelshagen						     LVM TOOLS							       LVRENAME(8)