Collecting SSD dump files using the CLI

You can use the command-line interface (CLI) to collect dump files from solid-state drives (SSDs).

To collect internal log files from solid-state drive (SSD) MDisks, run the triggermdiskdump command. Subsequently, you can list, delete or copy the dump files.

The triggermdiskdump command generates a dump file and saves it in the /dumps/mdisk directory on the node that contains the SSD.

  1. Issue the svctask triggermdiskdump CLI command.

    The following example shows the CLI format for generating a dump file for the specified SSD MDisk:

    svctask triggermdiskdump mdisk_id | mdisk_name
    
  2. Issue the svcinfo lsmdiskdumps command to list files in the /dumps/drive directory on the specified node.

    The following example shows the CLI format for listing the dump files for the specified node:

    svcinfo lsmdiskdumps node_id | node_name
    
  3. Issue the svctask cleardumps command to delete all files from the /dumps directory and all subdirectories on the specified node. To delete files from a subdirectory of /dumps only, specify the -prefix parameter.

    The following example shows the CLI format for deleting all dump files from the specified node:

    svctask cleardumps node_id | node_name
    

    The following example shows the CLI format for deleting only the dump files in the specified /elogs/ directory:

    svctask cleardumps -prefix "/dumps/elogs/*" 
    
  4. Issue the svctask 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 after migrating data from the configuration node.

    The following example shows the CLI format for copying all dump files from the specified node to the configuration node:

    svctask cpdumps -prefix /dumps node_id | node_name
    
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2003, 2009. All Rights Reserved.