Skip to main content
NetApp Knowledge Base

CONTAP-535854: SnapMirror restore from Archival tier causes node to panic and reboot

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

Issue

  • Data residing in an Archival tier of an Object Store, rather than the Standard tier, needs to be restored.
  • When attempting a SnapMirror restore of a Full Volume with tiering (cloud object store to *_vault_restore volumes), the restore attempt triggers a panic and causes a controller distruption.

Panic_Message: thread stack overflow on cpu 7: rip 0xffffffff8c180ee3, rsp 0xfffff68046f78ff0,rbp 0xfffff68046f79570 in SK process repl_Handle_reg on release 9.16.1P6 (C)
  • When the data being restored resides in an Archival tier of an Object Store, a Single File Restore or Directory Restore can also result in panic and controller disruption.

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.