Skip to main content
NetApp Knowledge Base

Disk assignment fails while EMS periodically logs diskown.ownerReservationMismatch

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

Applies to

  • ONTAP 9
  • Advanced Disk Partitioning (ADP)

Issue

  • The diskown.ownerReservationMismatch errror is shown in the event log show output:

8/13/2021 13:13:13    ERROR         diskown.ownerReservationMismatch: disk 0d.01.13P1 (S/N XXX) is supposed to be owned by this node but has a persistent reservation placed by node partner-node(ID <partner-sysid>).

  • Attempt to assign disk fails with error:
::> disk assign -disk 1.1.23 -data1 true -owner local-node
Error: command failed: Failed to assign disks. Reason: Cannot assign "1.1.13.P1" from this node. Try the command again on node "<partner-node>" (<partner-sysid>).
  • Or assign command run successfully but actually it fails:

Wed Oct 23 2024 11:16:37 +09:00 [kern_audit:info:2005]console :: system vserver:admin :: storage disk assign -owner local-node -disk 2.11.10 -data true :: Pending
Wed Oct 23 2024 11:16:38 +09:00 [kern_audit:info:2005]console :: system vserver:admin :: storage disk assign -owner local-node -disk 2.11.10 -data true :: Success

Wed Oct 23 11:16:38 JST [partner-node: sanown_io: diskown.changingOwner:info]: Changing ownership of disk 0a.11.10P1 (S/N yyyyyyyyy) from node "unowned" (ID -1, DR home ID -1) to node "local-node" (ID 5xxxxxxx, DR home ID -1).
Wed Oct 23 11:16:45 JST [partner-node: sanown_io: diskown.releasingMismatchedReservation:notice]: reservation process is releasing reservation on disk 0a.11.10P1 (S/N yyyyyyyyy) as it is owned by local-node (ID 5xxxxxxx)
Wed Oct 23 11:22:54 JST [partner-node: cfdisk_config: cf.disk.inventory.mismatch:error]: Status of the disk 0a.11.10P1 (60000399:F82B9ADC:500A0981:00000001:00000000:00000000:00000000:00000000:00000000:00000000) has recently changed or the node (local-node) is missing the disk.
Wed Oct 23 11:22:54 JST [partner-node: cfdisk_config: callhome.sfo.miscount:error]: Call home for HA GROUP ERROR: DISK/SHELF COUNT MISMATCH

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.