vgimport.1m (2010 09)

v
vgimport(1M) vgimport(1M)
NAME
vgimport - import an LVM volume group onto the system
SYNOPSIS
/usr/sbin/vgimport
[-m mapfile ][
-p][-v] vg_name pv_path ...
/usr/sbin/vgimport
[-m mapfile ][
-p][-v][-f infile] vg_name
/usr/sbin/vgimport -m
mapfile [-N][
-C][-v][-p] -s vg_name
DESCRIPTION
The
vgimport command adds the specified volume group to the system. The physical volumes, specified
as pv_path ..., are scanned to obtain the volume group information and logical volume information. This
command works much like vgcreate. A user may explicitly create the vg_name directory and the
group file before importing the volume group. If absent, the
vgimport command will automatically
create the directory and the
group file, assigning the minor number as explained in the
vgcreate com-
mand man page (see vgcreate(1M)). The vg_name is added to the
/etc/lvmtab or /etc/lvmtab_p
file, and the associated logical volume device files are added to the system.
vgimport assumes that the volume group information has already been created on the physical
volumes.
This command is useful in conjunction with the
vgexport command (see vgexport (1M)), to move volume
groups from one system to other systems within a high availability cluster.
vgimport creates logical volume device files under the vg_name directory using the naming convention
given in mapfile or using the default naming convention used by the lvcreate command (see
lvcreate (1M)).
The
vgimport command reconstructs the newly imported volume group entry in the /etc/lvmtab or
/etc/lvmtab_p file. The order of the disks belonging to the newly imported volume group could be
different than it was before.
When a bootable volume group is imported (volume groups version 1.0 and 2.2 or higher only), the boot
information present in the boot disks might be incorrect due to the change in the order of disks in the
/etc/lvmtab or /etc/lvmtab_p files. This is because the boot information on the boot disks
assumes a certain order of disks in /etc/lvmtab or /etc/lvmtab_p
and requires a resynchroniza-
tion of this information after the first activation of a newly imported bootable volume group. To resyn-
chronize the information on the boot disk after the first activation of a newly imported bootable volume
group, run the
lvlnboot command in recovery mode (-R option).
vgimport does not activate the imported volume group due to the many possible options at volume
group activation time. To activate the volume group once it has been successfully imported, use the
vgchange command (see vgchange (1M)).
Options and Arguments
vgimport recognizes the following options and arguments:
pv_path The block device path names of a physical volume. This argument is not used with
the
-s and related options.
vg_name The path name of the volume group.
-m mapfile Specify the name of the file from which logical volume names and numbers are to be
read. This option is optional when used as in the first command line format of the
SYNOPSIS. If this option is not specified, logical volume names are created using
the default naming convention lvolN where N is the decimal representation of logi-
cal volume minor number. When used with the -s option, the volume group
specified in the mapfile can be shared among the exporting system and the import-
ing systems.
-N Configure the volume group by populating persistent device special files in the
/etc/lvmtab or /etc/lvmtab_p file, corresponding to the volume group,
vg_name. (See intro (7) for information about device special files.) This option can
only be used with -s option. If vgimport is invoked without a -N option, legacy
device special files will be used to populate the /etc/lvmtab or
/etc/lvmtab_p file.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1