Veritas Volume Manager 5.0.1 Migration Guide, HP-UX 11i v3, First Edition, November 2009

Table 1-1
A conceptual comparison of LVM and VxVM (continued)
DescriptionVxVM termLVM term
In LVM, import adds a volume group
to the system and the volume group
information to /etc/lvmtab but does
not make the volumes accessible. The
volume group must be activated by
the vgchange -a y command to
make volumes accessible.
In VxVM, import imports a disk group
and makes the disk group accessible
by the system.
ImportImport
In LVM, the bad block pool provides
for the transparent detection of bad
disk sectors, and the relocation of data
from bad to good disk sectors.
The bad block reallocation feature
does not exist in VxVM because the
vectoring of bad blocks is now done
by most hardware.
No similar termBad block pool
The /etc/lvmtab file contains
information about the volume groups
that are accessible by a system.
No similar term/etc/lvmtab
Coexistence of VxVM and LVM disks
Both LVM disks and VxVM disks can exist together on a system. The LVM disks
are detected and displayed as such by VxVM. LVM disks are not selected by VxVM
for initialization, addition, or replacement.
Both LVM and VxVM utilities are aware of the other volume manager, and will
not overwrite disks that are being managed by the other volume manager unless
conversion or rollback is being performed between LVM logical volumes and VxVM
volumes.
Note: The above behavior is displayed on both LVM version 1 and version 2 volume
groups.
17VxVM and LVM
Coexistence of VxVM and LVM disks