Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

The disks may be considered invalid due to a mismatch between the host ID in
their configuration copies and that stored in the /etc/vx/volboot file.
To clear locks on a specific set of devices, use the following command:
# vxdisk clearimport devicename ...
To clear the locks during import, use the following command:
# vxdg -C import diskgroup
Warning: Be careful when using the vxdisk clearimport or vxdg -C import
command on systems that see the same disks via a SAN. Clearing the locks allows
those disks to be accessed at the same time from multiple hosts and can result in
corrupted data.
A disk group can be imported successfully if all the disks are accessible that were
visible when the disk group was last imported successfully. However, sometimes
you may need to specify the -f option to forcibly import a disk group if some disks
are not available. If the import operation fails, an error message is displayed.
The following error message indicates a fatal error that requires hardware repair
or the creation of a new disk group, and recovery of the disk group configuration
and data:
VxVM vxdg ERROR V-5-1-587 Disk group groupname: import failed:
Disk group has no valid configuration copies
The following error message indicates a recoverable error.
VxVM vxdg ERROR V-5-1-587 Disk group groupname: import failed:
Disk for disk group not found
If some of the disks in the disk group have failed, you can force the disk group to
be imported by specifying the -f option to the vxdg import command:
# vxdg -f import diskgroup
Warning: Be careful when using the -f option. It can cause the same disk group
to be imported twice from different sets of disks. This can cause the disk group
configuration to become inconsistent.
See “Handling conflicting configuration copies” on page 243.
Creating and administering disk groups
Moving disk groups between systems
228