You can use the command-line interface (CLI)
to collect dump files from drives. To collect internal log files from
MDisks, run the triggerdrivedump command. Subsequently,
you can list, delete or copy the dump files.
The triggerdrivedump command
generates a dump file and saves it in the /dumps/drive directory
on the node that contains the drive.
- Issue the triggerdrivedump CLI command.
To generate a drive dump file for the specified drive,
issue this commandtriggerdrivedump drive_id
Remember: In the resulting output, note the
node_id that
contains the dump file.
For example, in:
...
Drive dump on node id [74] successfully created
...
The
node_id value is
74.
- Issue the lsdumps command
to list files in the /dumps/drive directory on
the specified node.
To list the drive dump files
for the specified node, issue this command: lsdumps -prefix
/dumps/drive node_id | node_name
This
resulting output displays the drive dumps:
id filename
0 drivedump_7802207-1_20_130326_102200
- Issue the cpdumps command to copy dump
files to the configuration node.
If the /dumps directory
on the configuration node becomes full before the copy completes,
no message is returned. To avoid this scenario, clear the /dumps directory
before migrating data to the configuration node
To
copy drive dump files from the specified node to the configuration
node, issue this command: cpdumps -prefix /dumps/drive node_id
| node_name
To show the copied drive dumps on the configuration node, issue this command:
lsdumps -prefix
/dumps/drive:
mcrsvt9a:superuser>lsdumps -prefix /dumps/drive
id filename
0 drivedump_7802207-1_20_130326_110053
1 drivedump_7802113-1_225_130326_110333
- To delete all files from the /dumps directory and all
subdirectories on the specified node, issue this command: cleardumps -prefix /dumps
node_id | node_name
To delete files from a subdirectory of /dumps only, specify the
-prefix parameter.
To delete drive dump files from the specified node, issue this command: cleardumps
-prefix /dumps/drive node_id|node_name node_id | node_name
The dump file can be created on a node other
than the configuration node if:
- The drive is connected to a node in a different I/O group
- Connectivity to the node is not complete at the time of the dump
The command feedback indicates on which node the dump appears.
If the dump appears on the configuration node you do not have to
copy the dump information to the configuration node.