Skip to main content
NetApp Knowledge Base

CONTAP-597102: WAFLIRON Inode Link-Count Mismatch Can Cause a System Panic

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

Issue

Under a specific sequence of WAFLIRON scans on a FlexVol volume with LDC enabled, a directory inode’s child link can be counted twice. This can cause WAFLIRON to detect an inode link-count mismatch and initiate a system panic.
The reported panic string is:
assertion "TRIGGERED BY THIS NODE - !!@@* FILE NEW BURT. sw/wafl *@@!!: WAFLIRON found a corruption: iron_set_inode_dirty - fileid = 98 in volume clone_0_src_ntapvol_0_none_fg_vol_955__0005@vserver:ad1b55eb-ce8f-11f0-b043-005056ac6281. WAFL inconsistent. Contact NetApp technical support."

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.