Skip to main content
NetApp Knowledge Base

AWS CVO long plex resync after a giveback

  1. Last updated
  2. Save as PDF
Views:
225
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
amazon_web_service
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Amazon Web Services (AWS)

Issue

  • A CVO HA pair recovered from a network issue in AWS, but after the giveback, plex resyncing is taking longer than expected.

Cause

  • The plex resync is restarting due to missing disks being reported in ONTAP.
  • If a disk is reported missing at any time during the resync, it will restart until the disks are re-assimilated back into CVO.
  • EMS log example showing start and stops for each resync interruption due to the missing disks, then the final resync completes hours later.
     
    • Mon Aug 15 18:19:17+0000 [theCVO-02: config_thread:raid.config.filesystem.disk.missing:info]: File system Disk/aggr3/plex1/rg0/0d.35 S/N [00000000A2RBWH8bmvwB] UID[00000000A2RBWH8bmvwB] is missing.
      Mon Aug 15 18:21:06 +0000[theCVO-02: config_thread: raid.rg.resync.start:notice]:local:/aggr3/plex1/rg0:start resynchronization (level 1)
    • Mon Aug 15 18:25:06 +0000 [theCVO-02:config_thread: raid.rg.resync.aborted:notice]:local:/aggr3/plex1/rg0:resynchronization aborted after 4:00.36
    • Mon Aug 15 19:47:03 +0000 [theCVO-02:config_thread: raid.rg.resync.start:notice]:local:/aggr3/plex1/rg0:start resynchronization(level 1)
    • Tue Aug 16 00:33:57 +0000 [theCVO-02:config_thread: raid.rg.resync.done:notice]:local:/aggr3/plex1/rg0:resynchronization completedin 4:46:54.56
       

Solution

  • If the disk missing errors stop, continue to monitor the resync using plex show from the cluster CLI until it finishes. No further action is needed.
  • If the resync process continually stops due to ongoing missing disk errors, please contact NetApp technical support and reference this KB for further assistance.

Additional Information

additionalInformation_text

Internal Notes

If disk missing errors persist in ONTAP, review the EBS volume statuses in the AWS console and note any errors, then contact AWS for support assistance.

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.