mmgetstate command
Displays the state of the GPFS daemon on one or more nodes.
Synopsis
mmgetstate [-L] [-s] [-v] [-Y] [-a | -N {Node[,Node...] | NodeFile | NodeClass}]
Availability
Available on all IBM Spectrum Scale editions.
Description
The mmgetstate command displays the state of the GPFS daemon on the specified nodes.
Parameters
- -a
- Displays the state of the GPFS daemon on all nodes in the cluster.
- -N {Node[,Node...] | NodeFile | NodeClass}
- Displays the state of the GPFS daemon information on the
specified nodes.
For general information on how to specify node names, see Specifying nodes as input to GPFS commands.
This command does not support a NodeClass of mount.
Options
- -L
- Displays the number of quorum nodes, the number of nodes that are up, the total number of nodes, the state of the GPFS daemon, and other information.
- -s
- Displays summary information, such as the number of local and remote nodes that are joined in the cluster and the number of quorum nodes.
- -v
- Displays intermediate error messages.
- -Y
- Displays the command output in a parseable format with a colon (:) as a field
delimiter. Each column is described by a header.Note: Fields that have a colon (:) are encoded to prevent confusion. For the set of characters that might be encoded, see the command documentation of mmclidecode. Use the mmclidecode command to decode the field.
The command recognizes and displays the following GPFS states:
- active
- The GPFS daemon is ready for operations.
- arbitrating
- A node is trying to form a quorum with the other available nodes.
- down
- The GPFS daemon is not running on the node or is recovering from an internal error.
- unknown
- An unknown value. The command cannot connect with the node or some other error occurred.
- unresponsive
- The GPFS daemon is running but is not responding.
Exit status
- 0
- Successful completion.
- nonzero
- A failure has occurred.
Security
You must have root authority to run the mmgetstate command.
The node on which the command is issued must be able to execute remote shell commands on any other node in the cluster without the use of a password and without producing any extraneous messages. For more information, see Requirements for administering a GPFS file system.
Examples
- To display the quorum, the number of nodes up, and the total number of nodes for the GPFS cluster, issue the following command:
mmgetstate -a -L
The system displays output similar to the following example:Node number Node name Quorum Nodes up Total nodes GPFS state Remarks ---------------------------------------------------------------------------- 1 c5n92 3 5 12 active 2 c5n94 3 5 12 active 3 c5n95 3 5 12 active quorum node 4 c5n96 3 5 12 active 5 c5n97 3 5 12 active quorum node 6 c5n98 3 5 12 active 7 c5n107 3 5 12 active quorum node 8 c5n108 3 5 12 active 9 c5n109 3 5 12 active quorum node 10 c5n110 3 5 12 down 11 c5n111 3 5 12 active quorum node 12 c5n112 3 5 12 active
The 3 under the Quorum column means that you must have three quorum nodes up to achieve quorum.
- In the following example, the cluster uses node quorum with tiebreaker disks. The asterisk (*)
in the Quorum field indicates that tiebreaker disks are being used:
The system displays output similar to the following example:mmgetstate -a -L
Node number Node name Quorum Nodes up Total nodes GPFS state Remarks ------------------------------------------------------------------------ 1 k5n91 5* 8 21 active 2 k5n92 5* 8 21 active quorum node 3 k5n94 5* 8 21 active 5 k5n96 5* 8 21 active 6 k5n97 5* 8 21 active quorum node 7 k5n98 5* 8 21 active 8 k5n99 5* 8 21 active quorum node
- To display summary information, issue this command:
The system displays output similar to the following example:mmgetstate -s
Node number Node name GPFS state ------------------------------------------ 5 c5n97 active Summary information --------------------- Number of nodes defined in the cluster: 12 Number of local nodes active in the cluster: 12 Number of remote nodes joined in this cluster: 0 Number of quorum nodes defined in the cluster: 5 Number of quorum nodes active in the cluster: 5 Quorum = 3, Quorum achieved