Skip to main content
NetApp Knowledge Base

CONTAP-738223: Node may panic when renaming a private metafile with a high inode number while directory link-count checking is active

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

Issue

A node may panic during a rename operation when the target is a private metafile whose inode number is above the range covered by the public link-count tracking structure. The panic string is:
PANIC: wafl_load_buf: wip = 0x0xfffff802d1fc3be0, fbn = 1134, level = 0, last logical block = 803, last physical block = 803, flags = 1,  in SK process wafl_exempt00

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.