Skip to main content
NetApp Knowledge Base

CONTAP-436651: High latency and LUN power on resets due to CG snap failure and 120 second SnapCenter timeout fencing i/o

Views:
10
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
5/9/2025, 11:05:27 AM

Issue

  • SnapCenter (or any ZAPI client) sends two ZAPI requests similar to below with 120 second timeout:

2025-03-20T12:12:37.6410145-07:00 DEBUG SMCore PID=[7200] TID=[86] <cg-start><snapshot>snapshot1</snapshot><volumes><volume-name>vol1</volume-name></volumes><user-timeout>120</user-timeout></cg-start>
2025-03-20T12:12:38.6009943-07:00 DEBUG SMCore PID=[7200] TID=[86] <cg-start><snapshot>snapshot1</snapshot><volumes><volume-name>vol1</volume-name><volume-name>vol2</volume-name></volumes><user-timeout>120</user-timeout></cg-start>
  • The snapshot timeout is 120 seconds.
  • Both snapshots have the same name (snapshot1).
  • vol1 is listed twice.
  • High latency is seen on a volume in the hundreds of milliseconds or seconds.
  • Power on resets are seen on a Linux host.
  • A disk group, volume group, or some striped set of LUNs span multiple FlexVols.

 

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.