Skip to main content
NetApp Knowledge Base

Disk left behind during aggregate healing

Views:
175
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • Stretch MetroCluster
  • ONTAP 9

Issue

After healing the data and root aggregates, one of the root aggregate disks is not returned to the node that is waiting for switchback:
 
Example:
 
  • Disaster Site perspective of root aggregate after aggregate healing

  Plex /DisasterSite_root/plex0 (online, normal, active, pool0)
    RAID group /DisasterSite_root/plex0/rg0 (degraded, block checksums)

      RAID Disk    Device         HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------    ------         ------------- ---- ---- ---- ----- --------------    --------------
      dparity      4b.125L1027    4b    50  0   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 
      parity       4b.125L1028    4b    50  1   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 
      data         FAILED                 N/A                        1695466/ -

 

  • Active Site perspective of root aggregate after the failed drive was recovered:

  Plex /DisasterSite_root/plex0 (online, normal, active, pool0)
    RAID group /DisasterSite_root/plex0/rg0 (double degraded, block checksums)

      RAID Disk    Device         HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------    ------         ------------- ---- ---- ---- ----- --------------    --------------
      dparity      FAILED                 N/A                        1695466/ -
      parity       FAILED                 N/A                        1695466/ -
      data         4b.125L1029    4b    50  2   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 

 

 

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.