Solaris Cluster 4.3 Failover Zones are Not Startable if SVM Metaset Name and Zpool Name are Identical
Last updated on JUNE 26, 2017
Applies to:Solaris Cluster - Version 4.3 to 4.3 [Release 4.3]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
There is a problem to start Solaris Cluster 4.3 failover zones where rpool name is zonename and a Solaris Volume Manager (SVM) metaset with the same name is available. It fails directly with Error Stop_Failed.
May 24 15:10:03 node1 SC[,SUNW.HAStoragePlus: [ID - daemon.err] 10,z01,z01_storage,hastorageplus_postnet_stop]: [ID 680838 daemon.error] Failed to check the existence of device group with name 'z01': Unexpected error
May 24 15:10:03 node1 Cluster.RGM.global.rgmd: [ID - daemon.err] [ID 938318 daemon.error] Method <hastorageplus_postnet_stop> failed on resource <z01_storage> in resource group <z01> [exit code <1>, time used: 0% of timeout <1800 seconds>]
We cannot also create an HAStorageplus.11 resource where rpool name and a metaset with the same name is available.
Recent upgrade done from Oracle Solaris Cluster (OSC) 4.2U2 to 4.3 or later 4.3 SRU.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms