Skip to main content
NetApp Knowledge Base

Unexpected Node halt due to disk reservation conflict

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

Applies to

  • ONTAP 9
  • 2 node Fabric Metrocluster 
  • ATTO Bridge firmware upgrade

Issue

  • Following an ATTO bridge firmware update, multiple disk reservation conflicts occurred which caused both nodes of a 2-node Fabric Metrocluster to halt.
  • Both nodes halting at the same time and a switchover was not possible
  • After the nodes rebooted successfully, multiple disks which experienced conflicts were marked container-type unknown, which resulted in the failure of one raid group and degradation of another

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.