You can use the command-line interface (CLI) to list the
virtual disks (VDisks) that are dependent on the status of a node.
If a node goes offline or is removed from a cluster, all
VDisks that are dependent on the node go offline. Before taking a
node offline or removing a node from a cluster, run the lsnodedependentvdisks command
to identify any node-dependent VDisks.
By default, the lsnodedependentvdisks command
also checks all available quorum disks. If the quorum disks are accessible
only through the specified node, the command returns an error.
Various scenarios can produce node-dependent
VDisks. The following examples are common scenarios in which the
lsnodedependentvdisks command
will return node-dependent VDisks:
- The node contains solid-state drives (SSDs) and
also contains the only synchronized copy of a mirrored VDisk.
- The node is the only node that can access an MDisk on the SAN
fabric.
- The other node in the I/O group is offline (all VDisks in the
I/O group are returned).
- Pinned data in the cache is stopping the partner node from joining
the I/O group.
To resolve (1), allow VDisk mirror synchronizations between
SSD MDisks to complete. To resolve
(2-4), bring any offline MDisks online and repair any degraded paths.
Note: The command lists the node-dependent VDisks at the
time the command is run; subsequent changes to a cluster require running
the command again.