| Measurement |
Description |
Measurement
Unit |
Interpretation |
| State |
Indicates the current state of the disk. |
|
The states of the disk along with the corresponding numeric values are indicated in the table below:
| Value |
State |
| 0 |
Failed |
| 1 |
Off |
| 2 |
Removed |
| 3 |
Binding |
| 4 |
Empty |
| 5 |
Enabled |
| 6 |
Expanding |
| 7 |
Unbound |
| 8 |
Powering up |
| 9 |
Ready |
| 10 |
Reduced power, Transitioning |
| 11 |
Hot spare ready |
| 12 |
Unknown |
| 13 |
Formatting |
| 14 |
Equlizing |
| 15 |
Rebuilding |
| 16 |
Full power |
| 17 |
Low power |
| 18 |
Unformatted |
| 19 |
Unsupported |
Note:By default, this measure reports any of the above-mentioned states while indicating the status of the disk. However, in the graph of this measure, states will be represented using their numeric equivalents only - i.e., 0 to 19. |
| Lun_count |
Indicates the number of Luns that are sharing this Disk |
Number |
Use the detailed diagnosis of this measure to know which LUNs are sharing this disk. |
| Busy |
Indicates the percent utilization of this disk. |
Percent |
The values in percent and their respective states are listed below:
- 90%-Critical(Disk Full)
- 80%-Major
- 60%-Minor
|
| Hard_read_errors |
Indicates the number of hard read errors in this disk. |
Number |
The values and their respective states are listed below:
- 10 - critical
- 5 - major
- 2 - minor
Increase in value of this measure indicates that the disk life is going to end or fail.
|
| Hard_write_errors |
Indicates the number of hard write errors in this disk. |
Number |
The values and their respective states are listed below:
- 10 - critical
- 5 - major
- 2 - minor
Increase in value of this measure indicates disk life is going to end or fail. |
| Soft_read_errors |
Indicates the number of uncorrected read errors in this disk. |
Number |
The values and their respective states are listed below:
- 10 - critical
- 5 - major
- 2 - minor
Increase in value of this measure indicates disk life is going to end or fail. |
| Soft_write_errors |
Indicates the number of uncorrected write errors in this disk. |
Number |
The values and their respective states are listed below:
- 10 - critical
- 5 - major
- 2 - minor
Increase in value of this measure indicates Disk life is going to end or fail. |
| Read_requests |
Indicates the rate at which read requests are made to this disk. |
Reqs/sec |
Compare the value of these measures across disks to isolate overloaded disks. This will also reveal irregularities in load balancing across disks. |
| Write_requests |
Indicates the rate at which write requests are made per second to this disk. |
Reqs/sec |
| Data_reads |
This measure indicates the rate at which data is read from this disk. |
MB/Sec |
|
| Data_writes |
Indicates the rate at which data is written to this disk. |
MB/Sec |
|
| Total_bandwidth |
This measure indicates the sum of data reads and data writes to this disk. |
MB/Sec |
|
| Disk_capacity |
Indicates the total size of this disk. |
GB |
|
| User_capacity |
Indicates the amount of space on this disk that is assigned to bound LUNs. |
GB |
|
| Used_percent |
Indicates the percentage of space in this disk that is currently in use. |
Percent |
Ideally, the value of this measure should be low. A consistent increase in this value could indicate a gradual, but steady erosion of space in the disk. |
| Read_retry |
Indicates the number of times read requests to this disk were retried. |
Number |
A low value is desired for this measure. |
| Write_retry |
Indicates the number of times write requests to this disk were retried. |
Number |
A low value is desired for this measure. |
| Remap_sector |
Indicates the number of sectors on this disk that were remapped to new locations on the disk due to read/write errors. |
Number |
A low value is desired for this measure. |
| Request_service_time |
Indicates the time taken by this disk to service requests. |
Secs |
A high value is typically indicative of a request processing bottleneck in the disk. Compare the value of this measure across disks to know which disks are experiencing significant latencies. |