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 will not need to access or modify these files.
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.
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.
Do not edit this file. If you change this file, you could corrupt your Solaris Volume Manager configuration or be unable to recover your Solaris Volume Manager configuration.
If your system loses the information 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.
The md.conf configuration file is read by Solaris Volume Manager at startup. You can edit two fields in this file: nmd, which sets the number of volumes (metadevices) that the configuration can support, and md_nsets, which is the number of disk sets. The default value for nmd is 128, which can be increased to 8192. The default value for md_nsets is 4, which can be increased to 32. The total number of named disk sets is always one less than the md_nsets value, because the default (unnamed or local) disk set is included in md_nsets.
Keep the values of nmd and md_nsets as low as possible. Memory structures exist for all possible devices as determined by nmd and md_nsets, even if you have not created those devices. For optimal performance, keep nmd and md_nsets only slightly higher than the number of volumes you will use.
After changing the md.conf configuration file, you will need to do a reconfiguration reboot for the changes to take effect.
This file configures and starts Solaris Volume Manager at boot and allows administrators to start and stop the daemons.
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).)