Fix RAID metadata check

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

diff --git a/mdadm.conf-example b/mdadm.conf-example
index 9250f233fa0986e59c27a641788b7f5854ec7056..35a75d128a6948ac74485d39e63cc2beaacb6c58 100644 (file)
--- a/mdadm.conf-example
+++ b/mdadm.conf-example
@@ -15,9 +15,9 @@
 #      ARRAY lines specify information about how to identify arrays so
 #        so that they can be activated
 #
-# You can have more than one device line and use wild cards. The first 
+# You can have more than one device line and use wild cards. The first
 # example includes SCSI the first partition of SCSI disks /dev/sdb,
-# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second 
+# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
 # line looks for array slices on IDE disks.
 #
 #DEVICE /dev/sd[bcdjkl]1
@@ -34,7 +34,7 @@
 # If you want to ignore all DDF arrays (maybe they are managed by dmraid),
 # and only assemble 1.x arrays if which are marked for 'this' homehost,
 # but assemble all others, then use
-#AUTH -ddf hosthost -1.x +all
+#AUTO -ddf homehost -1.x +all
 #
 # ARRAY lines specify an array to assemble and a method of identification.
 # Arrays can currently be identified by using a UUID, superblock minor number,
@@ -59,7 +59,7 @@
 # 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
+#    mdadm --follow --scan & echo $! > /run/mdadm/mon.pid
 # If the lines are not found, mdadm will exit quietly
 #MAILADDR root@mydomain.tld
 #PROGRAM /usr/sbin/handle-mdadm-events