Solaris Cluster Exposing an EMC Array Special Logical Device (LUNz, VMCDB, Gatekeeper, etc ...) Can Cause Reservation Conflict Panic
Last updated on DECEMBER 13, 2017
Applies to:Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Solaris Cluster Geographic Edition - Version 3.0x to 4.3 [Release 3.0 to 4.3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Exposing EMC Array special logical device (LUNz, VMCDB, Gatekeeper, etc ...) to a clustered environment, may cause a panic, with a reservation conflict.
Refer to document 1006505.1 for assistance on identifying such logical device.
If these device are exposed to a Solaris Cluster node especially a Solaris Clustered environment, using scsi-2 Reservations, the cluster software will poll these disks (see 1008156.1).
When the cluster polls the reservation on such a disk, it may not match what the cluster expects, and the nodes may panic with a reservation conflict:
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