Skip to main content
NetApp Knowledge Base

Node reboot after giveback

  1. Last updated
  2. Save as PDF
Views:
416
Visibility:
Public
Votes:
1
Category:
data-ontap-8
Specialty:
CORE
Last Updated:

Applies to

Data ONTAP 8

Issue

  • Node reboot after givebck from partner node.

.Reservation conflict after wait-for-giveback complete.
Rebooting...
Uptime: 1h12m20s
System rebooting...

  • Console reports Reservation conflict found on this node's disks.

..Reservation conflict found on this node's disks!

  • Console reports cf.disk.inventory.mismatch:CRITICAL before performing giveback.

Jul 14 22:04:16 [localhost:cf.disk.inventory.mismatch:CRITICAL]: Status of the disk 0c.30.23 (5000CCA0:2E156358:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000) has recently changed or the node () is missing the disk.
Jul 14 22:04:16 [localhost:cf.disk.inventory.mismatch:CRITICAL]: Status of the disk 0c.30.0 (5000CCA0:2E15102C:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000) has recently changed or the node () is missing the disk.
Jul 14 22:04:16 [localhost:cf.disk.inventory.mismatch:CRITICAL]: Status of the disk 0c.30.1 (5000CCA0:2E153E94:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000) has recently changed or the node () is missing the disk.
Jul 14 22:04:16 [localhost:cf.disk.invent.mismatchalt:CRITICAL]: Status of some of the disks has changed or the node () is missing 336 disks (detailed logs have been throttled).

 

 

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.