Solaris Cluster until 4.0 Node Panic with Reservation Conflict Panic when Node is Rebooted or Logical Unit (LUN) added
(Doc ID 1564171.1)
Last updated on MARCH 14, 2017
Applies to:Solaris Cluster - Version 3.2 to 4.0 [Release 3.2 to 4.0]
Solaris Cluster Geographic Edition - Version 3.2 to 4.0 [Release 3.2 to 4.0]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
On a Solaris Cluster configuration with at least three nodes, when a logical unit or a node is leaving the cluster for any reason, remaining node may panic with the following stack:
The triggers are:
- a cluster made of more than 2 nodes
- the global_fencing is set to pathcount and/or the logical unit on which the reservation conflict was reported is using pathcount
- shared storage logical unit were recently added
- a node left the cluster
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!