What does the wafltop output mean and how can it be interpreted?
Applies to
- ONTAP 9
wafltop
command
Answer
- It tracks utilization of the following resources:
- CPU
- Disk I/O
- Memory
- NVLOG utilization
- The format of the volume name will be:
aggregate:volume:protocol:message
in the output
Output | Meaning |
---|---|
aggregate |
The name of the Aggregate the Volume resides in |
<aggregate>:volume |
The FlexVol being worked on |
<aggregate>:<volume>: |
Frontend CIFS, FCP, iSCSI, or NFS, or backend protocols like |
<aggregate>:<volume>: |
Write allocator |
<aggregate>:<volume>: dense |
Deduplication or storage efficiency |
<aggregate>:<volume>: zombie |
File deletions |
<aggregate>:<volume>: other |
A catchall for any other internal operations, such as WAFL scanners |
<aggregate>:<volume>: WAFL_SPINNP_<operation> |
Refers to ONTAP 9 protocol workloads, or user traffic Example: |
<aggregate>:<volume>: |
Refers to some internal WAFL operations that may not be classified in other operation types, but are background in nature Example: A FlexClone is being split |
<aggregate>:<volume>: |
Refers to anything passing to/from disk |
<aggregate>:<volume>: |
An internal WAFL message, but is only meant to be used by NetApp Employees only, but a few are provided below: |
<aggregate>:<volume>: |
refers to deduplication (scheduled/post-process or inline) |
*WAFL_SCAN_* |
|
Terminology:
Term | Meaning |
---|---|
CPU Utilization |
|
Latency histograms | System (internal) and client latency. |
Disk I/O operations | Reads and writes from disk in MB and in terms of RAID messages. |
NVLog utilization |
|
Memory utilization(Debug only) |
Shows buffer cache and inode cache usage in terms of MB used. Note: Not meant to be used for performance troubleshooting, but only by NetApp Engineering. |
I/O Utilization | I/O utilization refers to the amount of data read or written in MB/s and IOPS. |
Additional Information
additionalInformation_text