Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Solaris Volume Manager Administration Guide
Previous Next

Maintaining State Database Replicas

How to Check the Status of State Database Replicas

  1. Become superuser.
  2. To check the status of state database replicas, use one of the following methods:
    • From the Enhanced Storage tool within the Solaris Management Console, open the State Database Replicas node to view all existing state database replicas. For more information, see the online help.

    • Use the metadb command to view the status of state database replicas. Add the -i option to display an explanation of the status flags, as shown in the following example. See the metadb(1M).

Example 7-4 Checking the Status of All State Database Replicas
# metadb -i
        flags           first blk       block count
     a m  p  luo        16              8192            /dev/dsk/c0t0d0s7
     a    p  luo        8208            8192            /dev/dsk/c0t0d0s7
     a    p  luo        16400           8192            /dev/dsk/c0t0d0s7
     a    p  luo        16              8192            /dev/dsk/c1t3d0s1
      W   p  l          16              8192            /dev/dsk/c2t3d0s1
     a    p  luo        16              8192            /dev/dsk/c1t1d0s3
     a    p  luo        8208            8192            /dev/dsk/c1t1d0s3
     a    p  luo        16400           8192            /dev/dsk/c1t1d0s3
 r - replica does not have device relocation information
 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/lvm/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

A legend of all the flags follows the status. The characters in front of the device name represent the status. Uppercase letters indicate a problem status. Lowercase letters indicate an “Okay” status.

How to Delete State Database Replicas

You might need to delete state database replicas to maintain your Solaris Volume Manager configuration. For example, if you will be replacing disk drives, you want to delete the state database replicas before you remove the drives. Otherwise Solaris Volume Manager will report them as having errors.

  1. Become superuser.
  2. To remove state database replicas, use one of the following methods:
    • From the Enhanced Storage tool within the Solaris Management Console, open the State Database Replicas node to view all existing state database replicas. Select replicas to delete, then choose Edit⇒Delete to remove them. For more information, see the online help.

    • Use the following form of the metadb command:

      # metadb -d -f ctds-of-slice
      -d

      Specifies to delete a state database replica.

      -f

      Specifies to force the operation, even if no replicas exist.

      ctds-of-slice

      Specifies the name of the component that contains the replica.

      Note that you need to specify each slice from which you want to remove the state database replica. See the metadb(1M) man page for more information.

Example 7-5 Deleting State Database Replicas
# metadb -d -f c0t0d0s7

This example shows the last replica being deleted from a slice.

You must add the -f option to force the deletion of the last replica on the system.

Previous Next

 
 
  Published under the terms fo the Public Documentation License Version 1.01. Design by Interspire