Skip to main content
NetApp Knowledge Base

Disk utilization from read I/O requests might cause an ONTAP internal service failure

Last Updated:

Applies to



  • In rare scenarios, when read I/O requests generate 100 percent disk utilization for a prolonged period of time, such as greater than 10 minutes, the lower priority ONTAP system internal disk reads might timeout.
  • This might lead to other ONTAP bizarre symptoms such as:
    1. There is an unknown state of aggregates when doing an aggregate show
    2. Loss of uptime info for a particular node but that node is not in failover
    3. A discernable pause after listing of status for some nodes in the cluster

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
Scan to view the article on your device