projects / thirdparty / mdadm.git / blame
| Commit | Line | Data |
|---|---|---|
| 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 | # | |
| 18 | # You can have more than one device line and use wild cards. The first | |
| 19 | # example includes SCSI the first partition of SCSI disks /dev/sdb, | |
| 20 | # /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second | |
| 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 NB |
29 | # |
| 30 | # | |
| 31 | # ARRAY lines specify an array to assemble and a method of identification. | |
| 32 | # Arrays can currently be identified by using a UUID, superblock minor number, | |
| 33 | # or a listing of devices. | |
| 34 | # | |
| 5787fa49 | 35 | # super-minor is usually the minor number of the metadevice |
| 56eb10c0 NB |
36 | # UUID is the Universally Unique Identifier for the array |
| 37 | # Each can be obtained using | |
| 38 | # | |
| 39 | # mdadm -D <md> | |
| 40 | # | |
| 41 | #ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371 | |
| 5787fa49 | 42 | #ARRAY /dev/md1 super-minor=1 |
| 60f91664 | 43 | #ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1 |
| e0d19036 NB |
44 | # |
| 45 | # ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor | |
| 46 | # will then move a spare between arrays in a spare-group if one array has a failed | |
| 47 | # drive but no spare | |
| 48 | #ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1 | |
| 49 | #ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1 | |
| 50 | # | |
| 51 | # When used in --follow (aka --monitor) mode, mdadm needs a | |
| 52 | # mail address and/or a program. This can be given with "mailaddr" | |
| 53 | # and "program" lines to that monitoring can be started using | |
| 54 | # mdadm --follow --scan & echo $! > /var/run/mdadm | |
| 55 | # If the lines are not found, mdadm will exit quietly | |
| 56 | #MAILADDR root@mydomain.tld | |
| 57 | #PROGRAM /usr/sbin/handle-mdadm-events |