Skip to main content
NetApp Knowledge Base

CONTAP-448985: ONTAP cluster node reboots unexpectedly

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

Issue

ONTAP cluster node reboots unexpectedly:
PANIC: prod/common/wafl/free_cache.c:371: Assertion failure. in SK process sd_reformat_main on release 9.16.1P1 (C)

  • When SE (storage efficient) data is replicated from one platform to another, a conversion from the source compression algorithm to the algorithm supported on the destination is sometimes necessary.  This conversion allows the destination to maintain storage efficiency of the replicated data, and is the reformat referred to in the Panic string.
  • As part of this reformatting, memory is pre-allocated for this operation.
  • During this pre-allocation we should not context switch.
  • In this scenario, we inadvertently had a context switch while the preallocation was in progress.
  • The Assertion and associated panic happened when the pre-allocation slept on the initial CPU, and then woke on a different CPU.
  • This problem is being addressed in future versions of ONTAP.

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.