VERITAS Volume Manager 5.0 Migration Guide (September 2006)

40 Converting LVM to VxVM
Examples
The smallest disk in the Volume Group (vg08) does not have
sufficient private space for the conversion to succeed. There
is only enough private space for 392 VM Database records and
the conversion of Volume Group (vg08) would require enough
space to allow 399 VxVM Database records. This would roughly
translate to needing an additional 896 bytes available in the
private space. This can be accomplished by reducing the number
of volumes in the (vg08) Volume Group, and allowing that for
every volume removed, the number of Database records required
would be reduced by three. This is only a rough approximation,
however.
Hit RETURN to continue.
Example: list, listvg, and vxprint outputs of an LVM volume group before
and after conversion
The examples given below, shows the vxvmconvert listvg, list, and vxprint
output for an LVM volume group
vg08 converted to a VxVM disk group dg08.
Example of vxvmconvert listvg output before conversion of
volume group vg08
LVM VOLUME GROUP INFORMATION
NAME TYPE PHYSICAL VOLUME
vg00 ROOT c0t5d0
vg08 Non-Root c0t8d0
vg09 Non-Root c0t9d0
Example of the vxvmconvert list output which shows the disk
devices on a system
DEVICE DISK GROUP STATUS
c0t5d0 - - online
c0t8d0 - - LVM
c0t9d0 - - LVM
c0t10d0 disk01 rootdg online
c0t11d0 - - online
Disk group: rootdg
What does vxmvconvert list display?
The device indicates a physical disk, a disk with a name indicates if the disk is under
VxVM control, a group shows the disk group name, and the status indicates if it is an
LVM disk. If the status is online, that means VxVM acknowledges the disk but doesn’t
have it under its control.