Solaris Volume Manager (SVM): Understanding the Kernel Tunable Parameter "md:mirrored_root_flag" (Doc ID 1420334.1)

Last updated on NOVEMBER 16, 2016

Applies to:

Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.10.0 [Release 11.0]
Solstice DiskSuite Software - Version 4.2.1 to 4.2.1 [Release 4.0]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)


When a system under SVM (Solaris Volume Manager) control boots, SVM consults the state database to determine the configuration and condition of metadevices. The state database is contained in replicas distributed over multiple disks.

SVM has a set of rules to determine the health of the state database itself. These rules take into account the possibility that some replicas may reside on disks with hardware problems or other operational issues. SVM requires that half of all state database replicas be available during normal operation. If more than half become unavailable, the system will panic to protect itself.

SVM requires that one more than half of all state database replicas be available at boot time, as a way to protect against the possibility of stale data. It is possible, in rare circumstances, that without this quorum rule, SVM may choose incorrectly when some replicas are broken.

Consider the following scenario. There are 3 replicas on each internal disk in a system with two internal disks. Let's call them disk1 and disk2. If disk1 experiences a transient failure, and then SVM comes along and makes a configuration change, the first attempt to write to the state database will mark the replicas on disk1 as broken. This state can only be written to the active replicas on disk2, of course.

The system is brought down, and at the next boot disk1 is working again, but disk2 has a transient failure making it inaccessible. Without a quorum rule requiring one more than half of all replicas to be healthy, the system would choose the stale database on disk1, which is all it can see. Remember that the replicas on disk1 do not "know" they are stale, and the replicas on disk2 are not available.

The purpose of this document is to explain the kernel tunable parameter md:mirrored_root_flag, which can modify the way SVM implements the quorum rule. This information is of particular interest for systems with only two internal disks available.

For a more complete discussion of the SVM state database, please consult the Solaris Volume Manager Administration Guide.


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