Solaris Cluster Reservation Conflict Panic in a Clustered Guest LDom When Rebooting Primary/Service Domain (Doc ID 1263669.1)

Last updated on FEBRUARY 23, 2017

Applies to:

Solaris Cluster - Version 3.2 12/06 and later
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)

Symptoms

You have a Solaris Cluster configured where one of the node is a guest logical domain.
And that domain paniced with the following stack trace:

Oct 1 08:38:11 node1 cl_dlpitrans: [ID 624622 kern.notice] Notifying cluster that this node is panicking
Oct 1 08:38:11 node1 unix: [ID 836849 kern.notice]
Oct 1 08:38:11 node1 panic[cpu30]/thread=2a104867ca0:
Oct 1 08:38:11 node1 unix: [ID 632503 kern.notice] Reservation Conflict
Oct 1 08:38:11 node1 Disk: /virtual-devices@100/channel-devices@200/disk@2

 

unix:panicsys+0x48()
unix:vpanic_common+0x78()
unix:panic+0x1c()
vdc:vdc_scsi_status+0x29c()
vdc:vdc_failfast_scsi_cmd+0x94()
vdc:vdc_failfast_check_resv+0x24()
vdc:vdc_failfast_thread+0x38()
unix:thread_start+0x4()
-- end of kernel thread's stack --

 

Cause

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