Solaris Cluster and HA VM Server Agent SUNW.ldom Data Corruption may Occur in a failover Guest Domain when "auto-boot?=true" is set
Last updated on DECEMBER 19, 2017
Applies to:Solaris Cluster - Version 3.2 and later
Solaris Cluster Geographic Edition - Version 3.2 and later
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on SPARC (64-bit)
In Solaris Cluster a Guest Domain (LDom) has been created in a 2 nodes cluster.
This failover LDom
* can be live migrated between the 2 cluster nodes
* is running Solaris and has zpools automatically imported when the domain is booted
* is bound and running on cluster node2 currently
Due to a hardware maintenance window, node1 is powered off.
And shortly after cluster node1 is powered on and booted, data corruption is detected in some zpools belonging to the fo-ldom.
The major event that triggered the data corruption is the power off/on done on cluster node1.
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