]> git.ipfire.org Git - thirdparty/mdadm.git/blob - mdadm.conf.man
mdadm-0.7.1
[thirdparty/mdadm.git] / mdadm.conf.man
1 MDADM.CONF(5) MDADM.CONF(5)
2
3
4
5 N\bNA\bAM\bME\bE
6 mdadm.conf - configuration for management of Software Raid
7 with mdadm
8
9 S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
10 /etc/mdadm.conf
11
12 D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
13 m\bmd\bda\bad\bdm\bm is a tools for creating an managing RAID devices
14 using the m\bmd\bd driver in Linux.
15
16 Some common tasks, such as assembling all arrays, can be
17 simplified by describing the devices and array in this
18 configuations file.
19
20
21 S\bSY\bYN\bNT\bTA\bAX\bX
22 The file should be seen as a collection of words separated
23 by white space (space, tab, or newline). Any word that
24 being with a hash sign (#) starts a comment and that word
25 together with the remainder of the line are ignored.
26
27 Any line that start with white space (space or tab) is
28 treated as though it were a continuation of the previous
29 line.
30
31 Empty lines are ignored, but otherwise each (non continua-
32 tion) line must start with a keyword as listed below. The
33 key words are case insensitve and can be abbreviated to 3
34 characters.
35
36 The keywords are:
37
38 D\bDE\bEV\bVI\bIC\bCE\bE A d\bde\bev\bvi\bic\bce\be line lists the devices (whole devices or
39 partitions) that might contain a component of an MD
40 array. When looking for the components of an
41 array, m\bmd\bda\bad\bdm\bm will scan these devices and no others.
42
43 The d\bde\bev\bvi\bic\bce\be line may contain a number of different
44 devices (separated by spaces) and each device name
45 can contain wild cards as defined by g\bgl\blo\bob\bb(7).
46
47 Also, there may be several device lines present in
48 the file.
49
50
51 A\bAR\bRR\bRA\bAY\bY
52
53 S\bSE\bEE\bE A\bAL\bLS\bSO\bO
54 mdadm (8), md (4).
55
56
57
58
59 MDADM.CONF(5)