Skip to main content
NetApp Knowledge Base

CONTAP-528672: Unexpected disk reservation conflict

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

Issue

  • An unexpected disk reservation conflict occurs on the same node where the disk was originally owned.
    Example:
    [ClusterA-01: disk_server_0: disk.reservationConflict.key:debug]: Device 0v.i1.1L51P3 reported SCSI RESERVATION CONFLICT status. 1 milliseconds ago, the reservation key reported by this device was <reservation-key>.

  • This may result in an unexpected node reboot.

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.