]> git.ipfire.org Git - thirdparty/mdadm.git/blame - mdadm.conf-example
Release mdadm-3.3.4
[thirdparty/mdadm.git] / mdadm.conf-example
CommitLineData
56eb10c0
NB
1# mdadm configuration file
2#
3# mdadm will function properly without the use of a configuration file,
4# but this file is useful for keeping track of arrays and member disks.
5# In general, a mdadm.conf file is created, and updated, after arrays
6# are created. This is the opposite behavior of /etc/raidtab which is
7# created prior to array construction.
8#
9#
10# the config file takes two types of lines:
11#
12# DEVICE lines specify a list of devices of where to look for
13# potential member disks
14#
15# ARRAY lines specify information about how to identify arrays so
16# so that they can be activated
17#
bcbb92d4 18# You can have more than one device line and use wild cards. The first
56eb10c0 19# example includes SCSI the first partition of SCSI disks /dev/sdb,
bcbb92d4 20# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
56eb10c0
NB
21# line looks for array slices on IDE disks.
22#
23#DEVICE /dev/sd[bcdjkl]1
24#DEVICE /dev/hda1 /dev/hdb1
25#
e0d19036
NB
26# If you mount devfs on /dev, then a suitable way to list all devices is:
27#DEVICE /dev/discs/*/*
28#
56eb10c0 29#
d1d3482b
N
30# The AUTO line can control which arrays get assembled by auto-assembly,
31# meaing either "mdadm -As" when there are no 'ARRAY' lines in this file,
32# or "mdadm --incremental" when the array found is not listed in this file.
33# By default, all arrays that are found are assembled.
34# If you want to ignore all DDF arrays (maybe they are managed by dmraid),
35# and only assemble 1.x arrays if which are marked for 'this' homehost,
36# but assemble all others, then use
0017a237 37#AUTO -ddf homehost -1.x +all
56eb10c0
NB
38#
39# ARRAY lines specify an array to assemble and a method of identification.
40# Arrays can currently be identified by using a UUID, superblock minor number,
41# or a listing of devices.
42#
5787fa49 43# super-minor is usually the minor number of the metadevice
56eb10c0
NB
44# UUID is the Universally Unique Identifier for the array
45# Each can be obtained using
46#
47# mdadm -D <md>
48#
49#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
5787fa49 50#ARRAY /dev/md1 super-minor=1
60f91664 51#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
e0d19036
NB
52#
53# ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor
54# will then move a spare between arrays in a spare-group if one array has a failed
55# drive but no spare
56#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
57#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
58#
59# When used in --follow (aka --monitor) mode, mdadm needs a
60# mail address and/or a program. This can be given with "mailaddr"
61# and "program" lines to that monitoring can be started using
96fd06ed 62# mdadm --follow --scan & echo $! > /run/mdadm/mon.pid
e0d19036
NB
63# If the lines are not found, mdadm will exit quietly
64#MAILADDR root@mydomain.tld
65#PROGRAM /usr/sbin/handle-mdadm-events