Skip to main content
NetApp Knowledge Base

MetroCluster switchback failed - Oplock recall timed out

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

Applies to

  • MetroCluster
  • Switchback aborted
  • CIFS Oplocks enabled

Issue

Switchback is aborted

ClusterA::> set advanced
ClusterA::*> metrocluster operation show

Failed to prepare the cluster for the switchback operation.
ClusterA::Node_A1 (fatal): Unable to process the DR operation for partners (Node_B1) due to an internal error (Oplock recall timed out because of CPU overload, slow CIFS client response, or a large number of open files.
Run "volume qtree oplocks -volume <vol> -qtree <tree> -vserver <name> -oplock-mode disable" for the volumes or qtrees of the participating vservers that have oplocks enabled.
Retry the MetroCluster command.
After the MetroCluster operation is complete, run "volume qtree oplocks -volume <vol> -qtree <tree> -vserver <name> -oplock-mode enable" to enable oplocks.).

 

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.