JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris Volume Manager Administration Guide     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information

Preface

1.  Getting Started With Solaris Volume Manager

2.  Storage Management Concepts

3.  Solaris Volume Manager Overview

4.  Solaris Volume Manager for Sun Cluster (Overview)

5.  Configuring and Using Solaris Volume Manager (Scenario)

6.  State Database (Overview)

7.  State Database (Tasks)

8.  RAID-0 (Stripe and Concatenation) Volumes (Overview)

9.  RAID-0 (Stripe and Concatenation) Volumes (Tasks)

10.  RAID-1 (Mirror) Volumes (Overview)

11.  RAID-1 (Mirror) Volumes (Tasks)

12.  Soft Partitions (Overview)

13.  Soft Partitions (Tasks)

14.  RAID-5 Volumes (Overview)

15.  RAID-5 Volumes (Tasks)

16.  Hot Spare Pools (Overview)

17.  Hot Spare Pools (Tasks)

18.  Disk Sets (Overview)

19.  Disk Sets (Tasks)

20.  Maintaining Solaris Volume Manager (Tasks)

21.  Best Practices for Solaris Volume Manager

22.  Top-Down Volume Creation (Overview)

23.  Top-Down Volume Creation (Tasks)

24.  Monitoring and Error Reporting (Tasks)

Solaris Volume Manager Monitoring and Reporting (Task Map)

Configuring the mdmonitord Command for Periodic Error Checking

How to Configure the mdmonitord Command for Periodic Error Checking

Solaris Volume Manager SNMP Agents Overview

Configuring the Solaris Volume Manager SNMP Agents

How to Configure the Solaris Volume Manager SNMP Agents

Limitations of the Solaris Volume Manager SNMP Agent

Monitoring Solaris Volume Manager With a cron Job

How to Automate Checking for Errors in Volumes

25.  Troubleshooting Solaris Volume Manager (Tasks)

A.  Important Solaris Volume Manager Files

B.  Solaris Volume Manager Quick Reference

C.  Solaris Volume Manager CIM/WBEM API

Index

Configuring the mdmonitord Command for Periodic Error Checking

Solaris Volume Manager includes the /usr/sbin/mdmonitord daemon. When a disk fails, Solaris Volume Manager detects the failure and generates an error. This error event triggers the mdmonitord daemon to perform a check of RAID-1 (mirror) volumes, RAID-5 volumes, and hot spares. However, you can also configure this program to actively check for errors at an interval that you specify.

How to Configure the mdmonitord Command for Periodic Error Checking

Edit the /lib/svc/method/svc-mdmonitor script to add a time interval for periodic checking.

  1. Become superuser.
  2. Open the /lib/svc/method/svc-mdmonitor script in the editor of your choice. Locate the following section in the script:
    $MDMONITORD
    error=$?
    case $error in
    0)      exit 0
            ;;
    
    *)      echo "Could not start $MDMONITORD. Error $error."
            exit 0
  3. Change the line that starts the mdmonitord command by adding a -t flag and the number of seconds between checks.
    $MDMONITORD -t 3600
    error=$?
    case $error in
    0)      exit 0
            ;;
    
    *)      echo "Could not start $MDMONITORD. Error $error."
            exit 0
            ;;
    esac
  4. Restart the mdmonitord command to activate your changes.
    # svcadm restart system/mdmonitor

    For more information, see the mdmonitord(1M) man page.