(no commit message)

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

diff --git a/mdadm.conf-example b/mdadm.conf-example
index 09c7989316d5dd22df230ccff942d4fde7d43bab..9250f233fa0986e59c27a641788b7f5854ec7056 100644 (file)
--- a/mdadm.conf-example
+++ b/mdadm.conf-example
@@ -27,6 +27,14 @@
 #DEVICE /dev/discs/*/*
 #
 #
+# The AUTO line can control which arrays get assembled by auto-assembly,
+# meaing either "mdadm -As" when there are no 'ARRAY' lines in this file,
+# or "mdadm --incremental" when the array found is not listed in this file.
+# By default, all arrays that are found are assembled.
+# 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
 #
 # ARRAY lines specify an array to assemble and a method of identification.
 # Arrays can currently be identified by using a UUID, superblock minor number,
@@ -40,7 +48,7 @@
 #
 #ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
 #ARRAY /dev/md1 super-minor=1
-#ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2
+#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
 #
 # 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