Skip to main content
NetApp Knowledge Base

WAFL Inconsistency and Node Down After Extended Power Off

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

Applies to

  • ONTAP 9
  • AFF/FAS Systems

Issue

  • After powering on an cluster that had been powered off for approximately two months, one node failed to boot and reported WAFL inconsistencies on the root aggregate. The following log messages were observed in AutoSupport and console:

    Tue Mar 03 16:53:26+0000 [node1:wafl_exempt02:wafl.raid.incons.buf:error]: WAFL inconsistent: bad block at VBN 8406877 (vvbn:12652616 fbn:1764 level:0) in public inode (fileid:4294967295 snapid:0 fixable:1 file_type:1 disk_flags:0x2 error:118 raid_set:1) in volume partner:vol0.

    [node1:callhome.root.vol.recovery.reqd:EMERGENCY]: Call home for ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED.

  • Additionally, repeated EMS messages such as raid_cksum_wc_blkErr_1, raid_multierr_bad_block_1, and wafl_raid_incons_buf_1 were reported.

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.