Skip to main content
NetApp Knowledge Base

WAFL metadata inconsistent errors after "vol move"

Views:
40
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9

Issue

  • After "vol move" of a volume, the following errors are observed in EMS

[?] Mon Jul 11 23:33:02 +0300 [node1: wafl_exempt00: wafl.raid.incons.buf:error]: WAFL inconsistent: bad block at VBN 2009380494 (vvbn:108163708 fbn:0 level:0) in public inode (fileid:667943 snapid:0 fixable:1 file_type:2 disk_flags:0x2 error:119 raid_set:1) in volume vol100@vserver:095a699b-0048-11ed-bc98-d039ea396092.
[?] Mon Jul 11 23:33:02 +0300 [node1: wafl_exempt00: callhome.wafl.inconsistent.block:alert]: Call home for WAFL INCONSISTENT BLOCK
[?] Mon Jul 11 23:33:02 +0300 [node1: wafl_exempt00: wafl.inconsistent.vol:error]: WAFL inconsistent: volume vol100@vserver:095a699b-0048-11ed-bc98-xxxxxxxxxxx is inconsistent. Note: Any new Snapshot copies might contain this inconsistency.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device