Skip to main content
NetApp Knowledge Base

Metrocluster: Giveback vetoed because aggr is being resynced

  1. Last updated
  2. Save as PDF
Views:
273
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP 9
  • Node in takeover

Issue

  • Output of storage failover show-giveback:
ClusterA::> storage failover show-giveback
               Partner
Node           Aggregate         Giveback Status
-------------- ----------------- ---------------------------------------------
ClusterA-01
               CFO Aggregates    Done
               aggr1_ClusterA
                                 Failed: Operation was vetoed by raid.
                                 Giveback vetoed: Cannot send all specified
                                 aggregates home. Use the "event log show
                                 -message-name
                                 gb.sfo.abort.raid.fm|gb.cfo.abort.raid.fm"
                                 command to get more information, and follow
                                 the provided corrective actions. To execute
                                 the giveback without checks, use the
                                 "override-vetoes" parameter.  Warning:
                                 overriding vetoes may result in a data
                                 service outage.
ClusterA-02
                                 No aggregates to give back
3 entries were displayed.
  • The output of storage failover show-giveback for the node that is waiting for the rest of its aggregates to be given back to might be:

aggr1_ClusterA            No aggregates to give back

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.