メインコンテンツまでスキップ

wafl.dinconsistent 。破損がない場合に表示される EMS メッセージ

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

環境

  • ONTAP 9
  • Data ONTAP 8

問題

  • ノードから次のようなメッセージが生成され、ボリュームにユーザへの影響は報告されません。

Message:wafl.inconsistent.dirent: WAFL inconsistent: wafl_lookup_path: bad entry {x0 12 snapid: 85524 977940221 1193}<weekly.2018-12-02_0015> in private directory {x20 0 snapid: 27326 970784039 1193} in volume vol1@vserver:86fdcb2c-2f2f-11e6-8d70-90e2bab0fc4c.

Description: This event occurs when a lookup results in an inconsistent directory entry. The `dfh' parameters represent the directory file handle, the `fh' parameters represent the requested file handle. Access to this directory entry is disabled until you you repair it by running wafliron.

Corrective Action: The volume is inconsistent. Wafliron should be run as soon as possible to clear this inconsistency; for a snapmirror target, rebuild from source or resync or if the inode is in a snapshot, delete the snapshot. Then contact NetApp technical support.

  • ボリュームを見ると、ボリュームがオンラインであり、正常に動作していて、不整合とマークされていないことがわかります。

Cluster01::> volume show -vserver svm1 -volume vol1 -fields state,is-inconsistent
vserver volume state   is-inconsistent
------- ------ ------- ---------------
svm1    vol1   online  false

 

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.