Skip to main content
NetApp Knowledge Base

Multiple panic events occur due to a potential in-memory corruption

Views:
48
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • AFF 8040

Issue

Multiple panic events occur:
  • Example1
PANIC: A potential in-memory corruption of file system metadata (private inode 91, level 1, fbn 0, incremental checksum mismatch) has been detected. Rebooting the node to keep the file system on disk unaffected. Contact NetApp technical support for help.
  • Example2
PANIC: Host memory checksum mismatch on WRITE VERIFY: Disk 0a.00.10, Disk Block #5250: Volume volume_name, FileId -1, File Block#0: Expected 0xad36bd6c, Recomputed as 0xbf6a0eec in SK process disk_server_0 on release 9.7P11 (C)

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.