将转储运行到 null 时出现 WAFL 不一致错误

最后更新
另存为PDF

Views:

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: core

Last Updated:

适用于

ONTAP 9
WAFL

问题描述

在 RW 卷上报告了以下 WAFL 不一致，并执行了dump to null。

[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.

转储为 null 在第 3 阶段失败。
一个新的 WAFL 不一致错误在 fileid:4201 的 VBN 39945885441 处被触发，但对于卷 vol1 上的新快照 ID 每次运行转储到 null 时都会发生。
此卷以前是 DP，现在源集群已停用。
"volume file show-inode" 命令抛出以下错误

::*> 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.