Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Disk assignment fails while EMS periodically logs diskown.ownerReservationMismatch

Views:
62
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 (ID <partner-sysid>).

  • Attempt to assign disk fails with error:
::> disk assign -disk 1.1.23 -data1 true -owner node-01
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>).
Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support