Skip to main content
NetApp Knowledge Base

CONTAP-750706: ONTAP node may reboot unexpectedly with "Failover Monitor: unable to transit - giveback process is hung (snapvault)" due to WAFL extent leak in wafl_spinnp_read_local when audit destination volume is full

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

Issue

  • Node panics with: "FailoverMonitor: unable to transit - giveback process is hung (snapvault)"
  • EMS event "wafl.memory.statusVeryLowMemory" fires repeatedly on the affected node prior to panic.
  • WAFL buffer pool memory is exhausted (~70M+ leaked extents, ~275GB), severely degrading I/O throughput.
  • During HA giveback,snapvault stop-secondary operation stalls on a WAFL_LOOKUP for /etc/log/snapmirror and exceeds the 600-second Failover Monitor timeout.
  • Predominantly observed on long-uptime nodes (>100 days) serving SnapMirror/SnapVault secondary workloads via SpinNP on partner-owned aggregates.

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.