Skip to main content
NetApp Knowledge Base

CONTAP-118215: IO disruption or high latency following SMas Planned Failover

  1. Last updated
    Apr 24, 2025
  2. Save as PDF
Views:
46
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:
4/24/2025, 2:31:12 PM

Issue

In certain ONTAP systems employing SnapMirror Active Sync (SMas) feature, some SMas source volumes may experience I/O disruptions following a planned failover operation on a different SMas relationship. This may also show up as sudden high latency in the range of 20 sec. 
 
Illustration
cg1_src              -----      cg1_dst
\- cg1_vol_src    -----      cg1_vol_dst
cg2_src              -----      cg2_dst
\- cg2_vol_src    -----      cg2_vol_dst
When snapmirror failover command is executed on cg1_dst, cg2_vol_src which belongs to cg2 can potentially face an IO disruption if cg1_vol_src and cg2_vol_src are located on the same node.
Volumes Affected

  • The defect is specific to SMas volumes and typically limited to a specific volume co-located with source endpoints of the CG undergoing planned failover.
  • Non-SMas volumes (for example, volumes in SM-S or SM-Async relationships) are not affected.

Symptoms
  • Users may notice high latency in reading or writing data — often a consistent latency of about 20 seconds.

 

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.