MDADM.CONF(5) MDADM.CONF(5) NNAAMMEE mdadm.conf - configuration for management of Software Raid with mdadm SSYYNNOOPPSSIISS /etc/mdadm.conf DDEESSCCRRIIPPTTIIOONN mmddaaddmm is a tool for creating, managing, and monitoring RAID devices using the mmdd driver in Linux. Some common tasks, such as assembling all arrays, can be simplified by describing the devices and array in this configuration file. SSYYNNTTAAXX The file should be seen as a collection of words separated by white space (space, tab, or newline). Any word that beings with a hash sign (#) starts a comment and that word together with the remainder of the line are ignored. Any line that start with white space (space or tab) is treated as though it were a continuation of the previous line. Empty lines are ignored, but otherwise each (non continua- tion) line must start with a keyword as listed below. The key words are case insensitive and can be abbreviated to 3 characters. The keywords are: DDEEVVIICCEE A ddeevviiccee line lists the devices (whole devices or partitions) that might contain a component of an MD array. When looking for the components of an array, mmddaaddmm will scan these devices and no others. The ddeevviiccee line may contain a number of different devices (separated by spaces) and each device name can contain wild cards as defined by gglloobb(7). Also, there may be several device lines present in the file. For example: DEVICE /dev/hda* /dev/hdc* DEV /dev/sd* DEVICE /dev/discs/disc*/disc AARRRRAAYY The ARRAY lines identify actual arrays. The second word on the line should be the name of the device where the array is normally assembled, such as //ddeevv//mmdd11. Subsequent words identify the array, or identify the array as a member of a group. If mul- tiple identities are given, then the array must match ALL identities to be considered a match. Each identity word has a tag, and equals sign, and some value. The options are: uuuuiidd== The value should be a 128 bit uuid in hexadeci- mal, with punctuation interspersed if desired. This must match the uuid stored in the superblock. ssuuppeerr--mmiinnoorr== The value is an integer which indicates the minor number that was stored in the superblock when the array was created. When an array is created as /dev/mdX, then the minor number X is stored. ddeevviicceess== The value is a comma separated list of device names. Precisely these devices will be used to assemble the array. Note that the devices listed there must also be listed on a DEVICE line. lleevveell== The value is a raid level. This is not nor- mally used to identify an array, but is sup- ported so that the output of mmddaaddmm ----eexxaammiinnee ----ssccaann can be use directly in the configuration file. ddiisskkss== The value is the number of disks in a complete active array. As with lleevveell== this is mainly for compatibility with the output of mmddaaddmm ----eexxaammiinnee ----ssccaann. ssppaarree--ggrroouupp== The value is a textual name for a group of arrays. All arrays with the same ssppaarree--ggrroouupp name are considered to be part of the same group. The significance of a group of arrays is that mmddaaddmm will, when monitoring the arrays, move a spare drive from one array in a group to another array in that group if the first array had a failed or missing drive but no spare. MMAAIILLAADDDDRR The mmaaiillaaddddrr line gives an E-mail address that alerts should be sent to when is running in ----mmoonnii-- ttoorr mode (and was given the ----ssccaann option). There should only be one MMAAIILLAADDDDRR line and it should have only one address. PPRROOGGRRAAMM The pprrooggrraamm line gives the name of a program to be run when mmddaaddmm ----mmoonniittoorr detects potentially inter- esting events on any of the arrays that it is moni- toring. This program gets run with two or three arguments, they being the Event, the md device, and possibly the related component device. There should only be one pprrooggrraamm line and it should be give only one program. SSEEEE AALLSSOO mmddaaddmm(8), mmdd(4). MDADM.CONF(5)