VERITAS Volume Manager 3.5 Migration Guide (August 2002)

Final 24 July 2002
66 VERITAS Volume Manager Migration Guide
Analysis shows that there is insufficient private space available to
convert this volume group
◆ Description
The error message indicates the maximumamount of recordsthat can be storedin the
private space, and how many records are needed to convert this particular volume
group.
◆ Action
You can reduce the number of records needed by reducing the number of logical
volumes in volume group by combining some of the logical volumes together.
Device device_name has the following bad blocks... Cannot convert
LVM Volume Group
◆ Description
Unlike LVM, VxVM does not support bad block revectoring at the physical volume
level. If there appear to be any valid bad blocks in the bad block directory of any disk
used in an LVM volume group, the group cannot be converted.
◆ Action
You have the following choices:
- Place a hardwarecall tohave the diskreplaced or havethe hardwareengineer use
the diagnostics (if applicable for this disk type) to re-vector the block. Then clear
the BBDIR as described below.
- If the errors were transient, or after the disk has been replaced, clearthe BBDIR as
follows:
a. Back up all the data associated with the physical volume.
b. Make a current backup of the LVM headers, for example:
# vgcfgbackup /dev/vg01
c. Close all the logical volumes associated with the volume group and then
deactivate the volume group.
d. Create a dummy link to the raw device, for example:
# ln /dev/rdsk/c0t0d0 /dev/rdsk/temp
e. Destroy the LVM headers using pvcreate -f on the dummy link, for example:
# pvcreate -f /dev/rdsk/temp