Solaris Cluster How to read/inkeys remove/scrub and write/register SCSI3 Reservation Keys on Shared Disks
Last updated on SEPTEMBER 13, 2017
Applies to:Solaris Cluster Geographic Edition - Version 3.1x to 4.3 [Release 3.1 to 4.3]
Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This document shows how to put back reservation keys on shared cluster disks, after they have been "scrubbed".
In Sun/Solaris Cluster 3.x software, for various reasons, SCSI3 reservation keys and reservations are sometimes removed from disks on purpose (for example, when moving storage area network(SAN) attached LUNs between clusters).
If a disk is inadvertently scrubbed, later when the cluster node accesses the device, it can cause "Reservation conflict" panic.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms