After Solaris Cluster upgrade and Solaris Volume Manager metaset configuration changes the system panic with metaset alignment error
Last updated on NOVEMBER 01, 2016
Applies to:Solaris Cluster - Version 3.2 12/06 to 3.3U1 5/11 [Release 3.2 to 3.3]
Solaris Cluster Geographic Edition - Version 3.2 12/06 to 3.3U1 5/11 [Release 3.2 to 3.3]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.10.0 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This issue applies to Solaris Cluster 3.x systems where Solaris was upgraded to higher Solaris update release. Furthermore configuration changes to the used Solaris Volume Manager diskset happened within this upgrade (2nd node was removed from the disksets)
The upgrade looked ok until doing the 'switch test' of the applications to the other node.
Then the following panics occurred on the nodes and it was not possible to start Solaris Cluster again:
The first panic "metaset alignment error", while performing dnlc_dir_lookup is a direct indicator for Bug:15254667, while for the second panic analysis of crashdump is required to identify that BUG unambiguously.
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