Creating a Storage I/O Diagnosis Task

Prerequisites

No nodes are in the Offline state.

Creating a Storage I/O Diagnosis and Analysis Task

1. Click next to System Diagnosis.
2. Set task parameters based on "Task Management" and Table 1.
   Figure 1 Creating a storage I/O diagnosis task
   

   Table 1 Parameters for creating a storage I/O diagnosis task

   Parameter	Description
   Task Name	Name of the task. The name must meet the following requirements: Contain only letters, digits, and special characters (including @#$ %^&*()[]<>._-!-+ and spaces). Contain 1 to 32 characters.
   Diagnosis Object	Select Storage I/O.
   Pressure Test Object	Pressure test object. Node name Node IP Address Logical Drive Name/File Name: name of the logical drive or file to be tested. This parameter is mandatory when Diagnosis Type is set to Common diagnosis. NOTE: A file pressure test will damage existing data in the file. To avoid file overwriting, do not use an existing file as the pressure test object. In addition, do not use the drive with any file system mounted as the object for the logical drive pressure test.
   Key Metrics	Pressure test parameters. Throughput, IOPS, and Latency are selected by default. Request Block Size (KB) Read/Write Mode Read/Write Ratio I/O Queue Depth I/O Engine Concurrency Direct I/O I/O Size (GB) Test Duration (s) Related Metrics Operation You can click Edit or Delete to perform corresponding operations on a model. NOTE: By default, 12 test models are available. You can add, edit, or delete test models as required. A maximum of 5 test models can be selected.
   Periodical Statistics	You can enable or disable this function. If it is disabled, data is collected at an interval of 500 ms.
   Statistical Period (ms)	Interval at which statistics are collected. The value ranges from 1 to 5000 ms.
   Size of the Collected File (MiB)	Size of the file to be collected. The default value is 10 MiB. The value ranges from 1 MiB to 100 MiB.

3. Click OK.

   You can click the icons next to the task name to perform the following operations:

   • : stops the analysis task. After an analysis task is stopped, the collected information will be deleted.
   • : restarts the analysis task. You can modify task parameter settings and restart an analysis task. This button is available when a task is canceled or fails.
   • : runs the analysis task again. The analysis task is renamed and restarted.
   • : deletes the analysis task. After a task is deleted, all data of this task will be deleted. Exercise caution when performing this operation.
   • : changes the task or report name. The report naming rule is the same as that of a task.
   

   The collection and analysis task will not be interrupted if you exit or switch to another page.

   After being authenticated, you can log in to the system again to view the execution progress of an ongoing task or the analysis report of a completed task.