VERITAS Volume Manager 3.1 Administrator's Guide

Cluster Functionality
Cluster-related Volume Manager Utilities and Daemons
Chapter 7 325
if the system administrator is fully aware of the possible consequences.
When a cluster is restarted, VxVM may refuse to auto-import a disk
group for one of the following reasons:
• A disk in that disk group is no longer accessible because of hardware
errors on the disk. In this case, the system administrator can
reimport the disk group with the force option using the following
command:
# vxdg -s -f import diskgroup
• Some of the nodes to which disks in the disk group are attached are
not currently in the cluster, so the disk group cannot access all of its
disks. In this case, a forced import is unsafe and should not be
attempted (because it can result in inconsistent mirrors).
If VxVM does not add a disk to an existing disk group (because that disk
is not attached to the same node(s) as the other disks in the disk group),
the system administrator can force-add the disk using the following
command:
# vxdg -f adddisk -g diskgroup [medianame=] accessname
Activating a shared disk group
A shared disk group can be activated using the following command:
# vxdg -g diskgroup set activation= mode
where mode is one of the following:
• exclusivewrite
• sharedwrite
• readonly
• sharedread
• off
Listing shared disk groups
vxdg can also be used to list shared disk groups. To display one line of
information for each disk group, use the following command:
# vxdg list