lsnodedependentvdisks

The lsnodedependentvdisks command displays the virtual disks (VDisks) that are dependent on the status of the specified node.

Syntax


>>- svcinfo -- -- lsnodedependentvdisks -- --+----------+-- ---->
                                             '- -nohdr -'      

>--+-----------------------+-- --+- node_id ---+---------------><
   '- -delim -- delimiter -'     '- node_name -'

Parameters

-nohdr: (Optional) By default, headings are displayed for each column of data in a concise style view, and for each item of data in a detailed style view. The -nohdr parameter suppresses the display of these headings.
Note: If there is no data to be displayed, headings are not displayed.
-delim delimiter: (Optional) By default in a concise view, all columns of data are space-separated. The width of each column is set to the maximum possible width of each item of data. In a detailed view, each item of data has its own row, and if the headers are displayed, the data is separated from the header by a space. Using the -delim parameter overrides this behavior. Valid input for the -delim parameter is a one-byte character. If you enter -delim : on the command line, the colon character (:) separates all items of data in a concise view; for example, the spacing of columns does not occur. In a detailed view, the data is separated from its header by the specified delimiter.
node_id | node_name: (Required) Specifies the node by its ID or name.

Description

The lsnodedependentvdisks command lists the VDisks that are dependent on the status of the specified node. If the node goes offline or is removed from the cluster, the dependent VDisks also go offline. Before taking a node offline or removing it from the cluster, you can use the command to ensure that you do not lose access to any VDisks.

The lsnodedependentvdisks command also checks the expected state of quorum disks. If all available quorum disks are only currently accessible through the specified node, the command returns an error. The quorum disks should be moved to MDisks that are accessible through all nodes.

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 VDisks that are dependent on the nodes at the time the command is run. Subsequent changes to your system require running the command again.

An invocation example

svcinfo lsnodedependentvdisks node1

The resulting output

vdisk_id       vdisk_name
0              vdisk0
1              vdisk1