Skip to main content
NetApp Knowledge Base

CONTAP-806461: WAFL inconsistent panic due to checksum mismatch after disk addition

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

Issue

On an ONTAP Select system running on VMware ESXi, the node may panic with:
PANIC: Unrecoverable metadata block (file <id>, block <id>, fbn <id>, level <N>, file type <N>) in aggregate <aggregate>. WAFL inconsistent.
The affected aggregate is a concatenated (RAID-0), unmirrored aggregate using Advanced Zoned Checksums (AZCS), backed by VMDKs on a VMware datastore. Core analysis shows a data block that reads back as all zeros under a valid stored checksum (E_PSEUDOBAD_BLOCK). Because RAID-0 has no parity or mirror, the lost block cannot be reconstructed, WAFL declares the aggregate inconsistent, and the system panics. Data unavailability persists until the aggregate/volume is recovered from backup or restoration procedures.

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.