Skip to main content
NetApp Knowledge Base

CONTAP-774599: WAFL metadata checksum mismatch during file writes can cause a node restart

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

Issue

During file writes on a system using compression data extents (CDE), ONTAP can detect an incremental checksum mismatch in protected WAFL metadata and restart the affected node. In an HA configuration, this can cause an unplanned failover.
The following exact diagnostic string was recorded:
!https://img.icons8.com/color-glass/4...h=14,height=14! text
DownloadCopy
 !!@@* FILE NEW BURT. *@@!!:Either someone (you?) forgot to use the right interfaces
(i.e. WAFL_SET_AND_PROTECT, WAFL_COPY_AND_PROTECT etc.) to modify a protected WAFL
metadata buffer (public inode 541, level 1, fbn 0, incremental checksum mismatch) OR
A potential in-memory corruption of WAFL metadata has been detected. For further
diagnosis of the problem you could try booting a DEBUG kernel or setting the
'wafl-metadata-page-protect?' bootarg to 'true' in a non-debug kernel
in SK process wafl_exempt05 on release R9.20.1RC1N_260804_0437 (C)

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.