Skip to main content
NetApp Knowledge Base

System Performance Degradation After Mass LUN Deletion

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

  • NetApp AFF-A300
  • ONTAP 9.13.1P9 (Cluster Mode)
  • iSCSI protocol environments
  • Systems experiencing mass LUN deletions and high aggregate utilization

Issue

  • A large number of LUNs were deleted (~106TB, ~40% of aggregate), causing:
    • High CPU utilization (background delete workload spiked to 30%)
    • WAFL_CP (Consistency Point) workload elevated to ~50%
    • Massive latency for client workloads (WAFLSuspOther latency in the hundreds of seconds)
    • Timeout and failure to access volumes for many instances
  • Example EMS log:
    Mon Dec 01 1:00:00+0000 [Node01:VdomAsyncTh_03:LUN.destroy:notice]: LUN /vol/vol_01/volume-d7s8d9s0-d8s7-7744-7283-875b7b6b9b5b destroyed (UUID:d7s8d9s0-d8s7-7744-7283-875b7b6b9b5b).
  • Business impact: No access to volume in write/read for affected clients.

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.