System Files and Startup Files
This section explains the files that are necessary for Solaris Volume Manager
to operate correctly. With the exception of a few specialized configuration changes, you do
not need to access or modify these files.
/etc/lvm/mddb.cf
Caution - Do not edit this file. If you change this file, you could corrupt your Solaris Volume Manager configuration.
The /etc/lvm/mddb.cf file records the locations of state database replicas. When state database replica locations change, Solaris Volume Manager makes an entry in the mddb.cf file that records the locations of all state databases. See the mddb.cf(4) man page for more information.
/etc/lvm/md.cf
The /etc/lvm/md.cf file contains automatically generated configuration information for the default (unspecified or local) disk set. When you change the Solaris Volume Manager configuration, Solaris Volume Manager automatically updates the md.cf file (except for information about hot spares in use). See the md.cf(4) man page for more information.
Caution - Do not edit this file. If you change this file, you could corrupt or be unable to recover your Solaris Volume Manager configuration.
If your system loses the information that is maintained in the state database, and as long as no volumes were changed or created in the meantime, you can use the md.cf file to recover your configuration. See How to Initialize Solaris Volume Manager From a Configuration File.
/kernel/drv/md.conf
The md.conf configuration file is read by Solaris Volume Manager at startup. The md.conf file contains the state database replica configuration information. As of Solaris 10, the nmd and md_nsets parameters are no longer edited manually. Solaris Volume Manager has been enhanced to configure volumes dynamically, as needed.
/etc/rcS.d/S35svm.init
This file configures and starts Solaris Volume Manager at boot and allows administrators to start and stop the daemons.
/etc/rc2.d/S95svm.sync
This file checks the Solaris Volume Manager configuration at boot, starts resynchronization of mirrors if necessary, and starts the active monitoring daemon. (For more information, see mdmonitord(1M).)
