mdadm-0.8

[thirdparty/mdadm.git] / mdadm.conf-example

diff --git a/mdadm.conf-example b/mdadm.conf-example
index f1a5b8fbfa2cfdd86480b48eeb9f592a48078a71..65c97b707073574219a9993b1b5320a4c093d55a 100644 (file)
--- a/mdadm.conf-example
+++ b/mdadm.conf-example
@@ -23,6 +23,9 @@
 #DEVICE /dev/sd[bcdjkl]1
 #DEVICE /dev/hda1 /dev/hdb1
 #
+# If you mount devfs on /dev, then a suitable way to list all devices is:
+#DEVICE /dev/discs/*/*
+#
 #
 #
 # ARRAY lines specify an array to assemble and a method of identification.
@@ -38,3 +41,17 @@
 #ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
 #ARRAY /dev/md1 superminor=1
 #ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2
+#
+# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
+# will then move a spare between arrays in a spare-group if one array has a failed
+# drive but no spare
+#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
+#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
+#
+# When used in --follow (aka --monitor) mode, mdadm needs a
+# mail address and/or a program.  This can be given with "mailaddr"
+# and "program" lines to that monitoring can be started using
+#    mdadm --follow --scan & echo $! > /var/run/mdadm
+# If the lines are not found, mdadm will exit quietly
+#MAILADDR root@mydomain.tld
+#PROGRAM /usr/sbin/handle-mdadm-events