Skip to main content
NetApp Knowledge Base

Aggregate does not start resync or reconstruct after a plex failure

Views:
1,079
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

 

Applies to

  • SyncMirror
  • Plex failure
  • Recomputing Parity
  • ONTAP 9

Issue

  • Syncmirror plex parity recomputation takes too long
  • After a SyncMirror plex failure several disks are marked as failed but no reconstruct or resync starts
  • Parity recomputation is ongoing

  Plex: /aggr1/plex2 (online, normal, resyncing, pool1)
   RAID Group /aggr1/plex2/rg0 (recomputing parity 1% completed, block checksums)
                                                              Usable Physical
     Position Disk                        Pool Type     RPM     Size     Size Status
     -------- --------------------------- ---- ----- ------ -------- -------- ----------
     dparity  2.41.23                      1   FSAS    7200   3.63TB   3.64TB (normal)
     parity   FAILED                       -   -          -   3.63TB        - (failed)
     data     FAILED                       -   -          -   3.63TB        - (failed)

 

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.