]>
Commit | Line | Data |
---|---|---|
56eb10c0 NB |
1 | .TH MDADM.CONF 5 |
2 | .SH NAME | |
3 | mdadm.conf \- configuration for management of Software Raid with mdadm | |
4 | .SH SYNOPSIS | |
5 | /etc/mdadm.conf | |
6 | .SH DESCRIPTION | |
7 | .PP | |
8 | .B mdadm | |
11a3e71d | 9 | is a tool for creating, managing, and monitoring RAID devices using the |
56eb10c0 NB |
10 | .B md |
11 | driver in Linux. | |
12 | .PP | |
13 | Some common tasks, such as assembling all arrays, can be simplified | |
2d465520 | 14 | by describing the devices and arrays in this configuration file. |
56eb10c0 NB |
15 | |
16 | .SS SYNTAX | |
17 | The file should be seen as a collection of words separated by white | |
18 | space (space, tab, or newline). | |
11a3e71d | 19 | Any word that beings with a hash sign (#) starts a comment and that |
2d465520 | 20 | word together with the remainder of the line is ignored. |
56eb10c0 | 21 | |
2d465520 | 22 | Any line that starts with white space (space or tab) is treated as |
56eb10c0 NB |
23 | though it were a continuation of the previous line. |
24 | ||
25 | Empty lines are ignored, but otherwise each (non continuation) line | |
2d465520 | 26 | must start with a keyword as listed below. The keywords are case |
e0d19036 | 27 | insensitive and can be abbreviated to 3 characters. |
56eb10c0 NB |
28 | |
29 | The keywords are: | |
30 | .TP | |
31 | .B DEVICE | |
32 | A | |
33 | .B device | |
34 | line lists the devices (whole devices or partitions) that might contain | |
35 | a component of an MD array. When looking for the components of an | |
36 | array, | |
37 | .B mdadm | |
2d465520 | 38 | will scan these devices (or any devices listed on the command line). |
56eb10c0 NB |
39 | |
40 | The | |
41 | .B device | |
42 | line may contain a number of different devices (separated by spaces) | |
43 | and each device name can contain wild cards as defined by | |
44 | .BR glob (7). | |
45 | ||
46 | Also, there may be several device lines present in the file. | |
47 | ||
5787fa49 NB |
48 | Alternatively, a |
49 | .B device | |
50 | line can contain the word | |
51 | .BR partitions . | |
52 | This will cause | |
53 | .I mdadm | |
54 | to read | |
55 | .I /proc/partitions | |
56 | and include all devices and partitions found there-in. | |
57 | .I mdadm | |
58 | does not use the names from | |
59 | .I /proc/partitions | |
60 | but only the major and minor device numbers. It scans | |
61 | .I /dev | |
62 | to find the name that matches the numbers. | |
63 | ||
11a3e71d NB |
64 | For example: |
65 | .IP | |
66 | DEVICE /dev/hda* /dev/hdc* | |
67 | .br | |
68 | DEV /dev/sd* | |
69 | .br | |
70 | DEVICE /dev/discs/disc*/disc | |
5787fa49 NB |
71 | .br |
72 | DEVICE partitions | |
11a3e71d | 73 | |
56eb10c0 NB |
74 | .TP |
75 | .B ARRAY | |
11a3e71d NB |
76 | The ARRAY lines identify actual arrays. The second word on the line |
77 | should be the name of the device where the array is normally | |
78 | assembled, such as | |
79 | .BR /dev/md1 . | |
e0d19036 NB |
80 | Subsequent words identify the array, or identify the array as a member |
81 | of a group. If multiple identities are given, | |
2d465520 NB |
82 | then a component device must match ALL identities to be considered a |
83 | match. Each identity word has a tag, and equals sign, and some value. | |
84 | The tags are: | |
11a3e71d NB |
85 | |
86 | .RS 4 | |
87 | .TP | |
88 | .B uuid= | |
89 | The value should be a 128 bit uuid in hexadecimal, with punctuation | |
90 | interspersed if desired. This must match the uuid stored in the | |
91 | superblock. | |
92 | .TP | |
93 | .B super-minor= | |
94 | The value is an integer which indicates the minor number that was | |
95 | stored in the superblock when the array was created. When an array is | |
96 | created as /dev/mdX, then the minor number X is stored. | |
97 | .TP | |
98 | .B devices= | |
56eedc1a NB |
99 | The value is a comma separated list of device names or device name |
100 | patterns. | |
101 | Only devices with names which match one entry in the list will be used | |
102 | to assemble the array. Note that the devices | |
11a3e71d NB |
103 | listed there must also be listed on a DEVICE line. |
104 | .TP | |
105 | .B level= | |
106 | The value is a raid level. This is not normally used to | |
107 | identify an array, but is supported so that the output of | |
108 | ||
109 | .B "mdadm --examine --scan" | |
110 | ||
111 | can be use directly in the configuration file. | |
112 | .TP | |
b83d95f3 NB |
113 | .B num-devices= |
114 | The value is the number of devices in a complete active array. As with | |
11a3e71d NB |
115 | .B level= |
116 | this is mainly for compatibility with the output of | |
56eb10c0 | 117 | |
11a3e71d | 118 | .BR "mdadm --examine --scan" . |
e0d19036 NB |
119 | |
120 | .TP | |
121 | .B spare-group= | |
122 | The value is a textual name for a group of arrays. All arrays with | |
123 | the same | |
124 | .B spare-group | |
125 | name are considered to be part of the same group. The significance of | |
126 | a group of arrays is that | |
127 | .B mdadm | |
128 | will, when monitoring the arrays, move a spare drive from one array in | |
129 | a group to another array in that group if the first array had a failed | |
130 | or missing drive but no spare. | |
11a3e71d | 131 | .RE |
e0d19036 NB |
132 | |
133 | .TP | |
134 | .B MAILADDR | |
135 | The | |
136 | .B mailaddr | |
137 | line gives an E-mail address that alerts should be | |
138 | sent to when | |
139 | .M mdadm | |
140 | is running in | |
141 | .B --monitor | |
142 | mode (and was given the | |
143 | .B --scan | |
144 | option). There should only be one | |
145 | .B MAILADDR | |
146 | line and it should have only one address. | |
147 | ||
148 | ||
149 | .TP | |
150 | .B PROGRAM | |
151 | The | |
152 | .B program | |
153 | line gives the name of a program to be run when | |
154 | .B "mdadm --monitor" | |
155 | detects potentially interesting events on any of the arrays that it | |
156 | is monitoring. This program gets run with two or three arguments, they | |
157 | being the Event, the md device, and possibly the related component | |
158 | device. | |
159 | ||
160 | There should only be one | |
161 | .B program | |
162 | line and it should be give only one program. | |
163 | ||
2d465520 NB |
164 | .SH EXAMPLE |
165 | DEVICE /dev/sd[bcdjkl]1 | |
166 | .br | |
167 | DEVICE /dev/hda1 /dev/hdb1 | |
168 | ||
169 | # /dev/md0 is known by it's UID. | |
170 | .br | |
171 | ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371 | |
172 | .br | |
173 | # /dev/md1 contains all devices with a minor number of | |
174 | .br | |
175 | # 1 in the superblock. | |
176 | .br | |
177 | ARRAY /dev/md1 superminor=1 | |
178 | .br | |
179 | # /dev/md2 is made from precisey these two devices | |
180 | .br | |
181 | ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2 | |
182 | ||
183 | # /dev/md4 and /dev/md5 are a spare-group and spares | |
184 | .br | |
185 | # can be moved between them | |
186 | .br | |
187 | ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df | |
188 | .br | |
189 | spare-group=group1 | |
190 | .br | |
191 | ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 | |
192 | .br | |
193 | spare-group=group1 | |
194 | ||
195 | MAILADDR root@mydomain.tld | |
196 | .br | |
197 | PROGRAM /usr/sbin/handle-mdadm-events | |
198 | ||
e0d19036 | 199 | |
56eb10c0 | 200 | .SH SEE ALSO |
11a3e71d NB |
201 | .BR mdadm (8), |
202 | .BR md (4). | |
56eb10c0 | 203 |