Solaris Volume Manager (SVM) Fixing State Database Replicas

(Doc ID 1005952.1)

Last updated on OCTOBER 17, 2017

Applies to:

Sun Solaris Volume Manager (SVM) - Version 11.9.0 to 11.11 [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)

Symptoms

Solaris Volume Manager (SWM) stores its configuration on state database replicas, also known as replicas, located on disk drives within the configuration. Due to the importance of replicas, at least three working replicas need to be present. These may be self-contained within a single disk partition, or dispersed across many disks on many disk partitions.

The metadb command is used to examine replicas and their current status. For further information regarding the status of a replica please use the "-i" option. Typically an upper case letter represents a faulted replica, but may also appear as "unknown".

Below there are six replicas across two disk drive partitions. The three replicas on c0t3d0s3 are working. The three replicas on c1t2d0s3 are faulted. 

#metadb -i
        flags    first blk     block count     
    a m  p  lu   16            1034          /dev/dsk/c0t3d0s3
    a    p  l    1050          1034          /dev/dsk/c0t3d0s3
    a    p  l    2084          1034          /dev/dsk/c0t3d0s3
    M    p       unknown       unknown       /dev/dsk/c1t2d0s3
    M    p       unknown       unknown       /dev/dsk/c1t2d0s3
    M    p       unknown       unknown       /dev/dsk/c1t2d0s3

       o - replica active prior to last mddb configuration change  
       u - replica is up to date 
       l - locator for this replica was read successfully
       c - replica's location was in /etc/opt/SUNWmd/mddb.cf
       p - replica's location was patched in kernel
       m - replica is master, this is replica selected as input
       W - replica has device write errors
       a - replica is active, commits are occurring to this replica
       M - replica had problem with master blocks
       D - replica had problem with data blocks
       F - replica had format problems
       S - replica is too small to hold current data base
       R - replica had device read errors-  



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