VERITAS Volume Manager 3.5 Administrator's Guide (September 2004)

Administering Cluster Functionality

Cluster Initialization and Conﬁguration

Chapter 10354

NOTE Once shutdown succeeds, the node has left the cluster. It is not

possible to access the shared volumes until the node joins the cluster

again.

Since shutdown can be a lengthy process, other reconﬁguration can take

place while shutdown is in progress. Normally, the shutdown attempt is

suspended until the other reconﬁguration completes. However, if it is

already too far advanced, the shutdown may complete ﬁrst.

NOTE The MC/ServiceGuard cmhaltnode command ﬁrst attempts to halt all

packages that are using shared disks before attempting to shut down

VxVM. If an application running outside of a deﬁned package performs

I/O to a shared volume, it can delay shutdown of VxVM, resulting in an

MC/ServiceGuard timeout.

Node Abort

If a node does not leave a cluster cleanly, this is because it crashed or

because some cluster component made the node leave on an emergency

basis. The ensuing cluster reconﬁguration calls the VxVM abort function.

This procedure immediately attempts to halt all access to shared

volumes, although it does wait until pending I/O from or to the disk

completes.

I/O operations that have not yet been started are failed, and the shared

volumes are removed. Applications that were accessing the shared

volumes therefore fail with errors.

After a node abort or crash, shared volumes must be recovered, either by

a surviving node or by a subsequent cluster restart, because it is very

likely that there are unsynchronized mirrors.

Cluster Shutdown

If all nodes leave a cluster, shared volumes must be recovered when the

cluster is next started if the last node did not leave cleanly, or if

resynchronization from previous nodes leaving uncleanly is incomplete.