Skip to main content
NetApp Knowledge Base

CONTAP-384790: High latency or access issues on FlexGroup after vol move

  1. Last updated
    Apr 16, 2025
  2. Save as PDF
Views:
11
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
4/16/2025, 11:00:56 AM

Issue

  • High latency is not observed from the constituent volume that was vol-moved, Instead it should have been observed on the other constituent/constituents that is/are on the same node  
  • High latency starts right after vol-move was done.
  • Access issues might be observed on the other constituent/constituents that is/are on the same node  
  • The FlexGroup being a FlexClone parent alone is not sufficient. The conditions that are needed are the following:
    • FlexGroup FlexClone Parent
    • Parent having >= 2 constituents on that node
    • Clone Constituents are also on that node and haven't been split. If the clone constituent/consituents is/are split or moved ot another node, then this problem dos not happen. IF there are multiple clones, then this applies to all the clones.

 

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.