Skip to main content
NetApp Knowledge Base

WAFL Inconsistency: Unrecoverable Metadata Block

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

Applies to

  • ONTAP 9

Issue

  • The WAFL inconsistency is caused by bad metadata. 
  • EMS Log shows the below.

Example:

Tue Oct 13 03:28:39 PDT [node_name: wafl_hipri: sk.panic:alert]: Panic String: Unrecoverable metadata block (file 20490, block 4995762153, fbn 702615040, level 1, file type 16) in aggregate aggr01_san05_snr. WAFL inconsistent. Please contact NetApp Global Services. in SK process wafl_hipri on release 8.2.3P3

 

 

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.