You can list the active IBM
Storage Scale
commands that are running on the file system manager node.
Most IBM
Storage Scale commands run within
the GPFS daemon on the file system manager node. Even if you
start a command on another node of the cluster, the node typically sends the command to the file
system manager node to be executed. (Two exceptions are the mmdiag command
and the mmfsadm dump command, which run on the node where they were
started.)
To list the active commands on the file system manager
node, follow these steps:
-
Enter the mmlsmgr command with no parameters to discover which node
is the file system manager node.
For more information on other options available for the
mmlsmgr command,
see
mmlsmgr command.
In the following example, the
mmlsmgr command reports that
node05
is the file system manager node:
# mmlsmgr
file system manager node
---------------- ------------------
gpfs1 192.168.145.14 (node05)
Cluster manager node: 192.168.145.13 (node03)
- Go to the command console on the file system manager node
and enter mmdiag --commands:
# mmdiag --commands
=== mmdiag: commands ===
CrHashTable 0x1167A28F0 n 2
cmd sock 24 cookie 2233688162 owner 38076509 id 0x3FE6046C2700000D(#13) uses 1
type 76 start 1460415325.957724 flags 0x106 SG none line 'mmdiag --commands'
cmd sock 12 cookie 521581069 owner 57606185 id 0x3FE6046C2700000C(#12) uses 1
type 13 start 1460415323.336314 flags 0x117 SG gpfs1 line 'mmrestripefs /dev/business1 -m'
The output indicates that two commands are running: the
mmdiag
--commands
command that you just entered and the
mmrestripefs command, which
was started from another node.
Note: The output contains two lines about active commands. Each line
begins with the term
cmd
and wraps to the next line. You might be interested in the
following fields:
start
- The system time at which the command was received.
SG
- The name of the file system, or
None
.
line
- The command as received by the GPFS
daemon.
The remaining input is detailed debugging data that is used for product support. For more
information on
mmdiag command output, see
For more
information, see mmdiag command.