esscheckdisks command

Checks attached disks for errors under various I/O operations.

Synopsis


esscheckdisks { --enclosure-listEnsloure-List --disk-list DiskList | --show-enclosure-list }
		            [ --iotest Io-Test ] [ --ioengine Io-Engine ]
		            [ --batch-size Batch-Size ] [ --duration Test-Duration]
                    [ --write-enable] [--iopath Io-Path] [--confirm]
		            [ -h | --help ]

Availability

Available with IBM Storage Scale System.

Description

The esscheckdisks command checks the attached drives for disk errors under various I/O operations before configuring (part of recovery group) them. At the end of the test, the number of errors (and net performance) per device is reported. This test is typically run on the EMS node. It can also be run on the I/O server node with the --local option. If any disk shows error (non-zero error count), it needs to be addressed before adding the drive in the recovery group. This is not a performance tool and performance statistics shown are approximate and relative to other disks in the same batch of the run. When run from the EMS node, summary results are saved in the /temp/checkdisk directory of the EMS node.

Parameters

--enclosure-list Ensloure-List: Specifies a list of enclosures on which to run the test. Use all to specify all attached enclosures.
--disk-list DiskList: Specifies a list of disks to be tested, for example: sdh, sdx, sdm.
Disks are not checked for potential write to local disks such as sda when --write-enable option is provided. --enclosure-list and --disk-list are mutually exclusive.
--show-enclosure-list: Displays a list of enclosures attached to I/O server nodes.
This list, or a subset of it can be used to provide input to --enclosure-list. Program exits after displaying the list.
--iotest IoTest: Specifies a comma-separated list of I/O operations for testing. Valid values are r (sequential read), w (sequential write), R (random read), W (random write), and a (all). The default is r (sequential read).
I/O tests are run in the sequence they are provided. For example, r,w,W,R,w,r. If a is provided alone or as a part of a sequence, the given sequence is replaced with r,w,R,W.
--ioengine Io-Engine: Specifies the I/O engine to use.
Valid values are g for gpfsperf, d for dd, or s for shred.
--batch-size Batch-Size: Specifies the batch size (number of disks tested at a time) of the test. Specify 0 for all attached drive in a single batch. Default batch size is 60. Maximum batch size must be limited to 120.
--duration Test-Duration: Specifies the duration of the test in seconds. Default is 30 seconds. Specify 0 to start and exit esscheckdisks while the I/O engine is running. It can be used to sequentially write to the end of the disk.
--write-enable: Enables read-write I/O operations to the drive. Default is read-only. For any test sequence that involves write operation, --write-enable must be specified.
--iopath Io-Path: Specifies a comma-separated list of I/O paths for test. Default is 0,1 indicating both paths. Applicable for PPC64 or PPC64LE systems only.
--confirm: Runs disk checks without prompting even if recovery group descriptor exists.
-h | --help: Displays usage information about this command and exits.

Exit status

0: Successful completion.
nonzero: A failure has occurred.

Restrictions

This command must be run on a system where there is no GPFS cluster configured.

This command must not be run on a system that has GPFS recovery groups.

Security

You must have root authority to run the esscheckdisks command.

Examples

This example shows esscheckdisks command running on node gssio1 and performing all tests (including write) in drives in all enclosures. Run:

esscheckdisks --iotest a --write-enable

The system displays output similar to this:

# [root@ess3k4a ~]# ESSENV=INSTALL esscheckdisks --enclosure-list all --iotest a --write-enable
2020-06-23T02:21:41.529854 Start running check disks
2020-06-23T02:21:41.781865 Disk check will be performed for host: ess3k4b
2020-06-23T02:21:42.415534 System architecture is x86_64
2020-06-23T02:21:42.415651 By default Path 0 will be taken for x86_64 types of node.
2020-06-23T02:21:42.415680 Path Lists: 0

2020-06-23T02:21:42.583868 Taking inventory of nvme disks
2020-06-23T02:21:49.646858 Using IO Engine: gpfsperf
2020-06-23T02:21:49.656844 Starting r test for 12 of 12 disks. Path: 0, duration 30 secs
2020-06-23T02:22:24.718011 Check disk analysis for r test Complete
2020-06-23T02:22:24.718170 Using IO Engine: gpfsperf
2020-06-23T02:22:24.719774 Starting w test for 12 of 12 disks. Path: 0, duration 30 secs
2020-06-23T02:22:59.785114 Check disk analysis for w test Complete

2020-06-23T02:22:59.785235 Using IO Engine: gpfsperf
2020-06-23T02:22:59.786783 Starting R test for 12 of 12 disks. Path: 0, duration 30 secs
2020-06-23T02:23:34.851447 Check disk analysis for R test Complete
2020-06-23T02:23:34.851573 Using IO Engine: gpfsperf
2020-06-23T02:23:34.853185 Starting W test for 12 of 12 disks. Path: 0, duration 30 secs
2020-06-23T02:24:09.918940 Check disk analysis for W test Complete

Location

/opt/ibm/ess/tools/bin