WAFL inconsistency error when running dump to null
Applies to
- ONTAP 9
- WAFL
Issue
- Following WAFL inconsistency was reported on the RW volume and dump to null was performed.
[cluster1-02: wafl_exempt02: wafl.raid.incons.buf:error]: WAFL inconsistent: bad block at VBN 39945885441 (vvbn:2995411778 fbn:0 level:0) in public inode (fileid:4201 snapid:946 fixable:0 file_type:2 disk_flags:0x2 error:120 raid_set:1) in volume VOL1@vserver:cad0ac63-9115-11ef-aa35-xxxxxxb9898.
[cluster1-02: wafl_exempt02: callhome.wafl.inconsistent.block:alert]: Call home for WAFL INCONSISTENT BLOCK
[cluster1-02: ndmp_session_0: dump.inconsistent.wafl_metadata:error]: Dump of source path (/SVM/vol1), Snapshot copy ID (946): WAFL metadata inconsistent due to disk errors. Aborting the backup.
- Dump to null fails at phase 3.
- A new WAFL inconsistent error is triggered on the fileid:4201 at VBN 39945885441 but for a new snapshot ID on the volume vol1 every time dump to null is run.
- This volume was previously DP and now the source cluster is decommissioned.
- "volume file show-inode" command throws the following error
::*> volume file show-inode -vserver svm -volume vol1 -inode-number 4201
Error: show failed: Unable to get inode information for inode "4201" in volume "vol1" in vserver "svm". Reason: The parent info is missing, it has to yet be loaded.