Solaris Volume Manager (SVM) Node/Server/System Panic with "md: Panic due to lack of DiskSuite state" (Doc ID 1005440.1)

Last updated on FEBRUARY 13, 2017

Applies to:

Solaris Cluster - Version 3.0 to 4.3 [Release 3.0 to 4.3]
Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [Release 11.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

System will panic with:

panic string:   md: Panic due to lack of DiskSuite state
database replicas. Fewer than 50% of the total were available,
so panic to ensure data integrity.

 

Note: similar panic can also happen without disksets, metasets or Solaris Cluster present. SVM has local state database replicas for root and local disk and has a separate replica for disksets aka metasets on shared disks. Both replicas require a majority quorum greater than 50% quorum to be accessed and changed. When this requirement is not met the system will paniced by md driver as designed.

 

Changes

Disk in diskset was repartitioned after being added to the diskset. 

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