Switch from /lib/init/rw to /dev for early-boot files.

[thirdparty/mdadm.git] / mdmon.8

diff --git a/mdmon.8 b/mdmon.8
index df9dfbcee7c0a172fd1b842d0414789230c80923..0c24732f85c2b234c50bd3743dc459c6660bc749 100644 (file)
--- a/mdmon.8
+++ b/mdmon.8
@@ -1,5 +1,5 @@
 .\" See file COPYING in distribution for details.
-.TH MDMON 8 "" v3.1.1
+.TH MDMON 8 "" v3.1.2
 .SH NAME
 mdmon \- monitor MD external metadata arrays
 
@@ -157,6 +157,14 @@ This tells mdmon to find any active containers and start monitoring
 each of them if appropriate.  This is normally used with
 .B \-\-takeover
 late in the boot sequence.
+A separate
+.I mdmon
+process is started for each container as the
+.B \-\-all
+argument is over-written with the name of the container.  To allow for
+containers with names longer than 5 characters, this argument can be
+arbitrarily extended, e.g. to
+.BR \-\-all-active-arrays .
 
 .PP
 Note that
@@ -178,6 +186,11 @@ mounted there are special considerations when the root filesystem is
 mounted from an
 .I mdmon
 monitored device.
+Note that in general
+.I mdmon
+is needed even if the filesystem is mounted read-only as some
+filesystems can still write to the device in those circumstances, for
+example to replay a journal after an unclean shutdown.
 
 When the array is assembled by the
 .B initramfs
@@ -195,7 +208,7 @@ and
 .B .sock
 file on.  The particular filesystem to use is given to mdmon at compile
 time and defaults to
-.BR /lib/init/rw .
+.BR /dev/.mdadm .
 
 This filesystem must persist through to the end of the boot sequence.
 
@@ -228,7 +241,7 @@ filesystem, like the root filesystem, should be remounted read-only.
 
 .SH EXAMPLES
 
-.B "  mdmon \-\-all \-\-takeover"
+.B "  mdmon \-\-all-active-arrays \-\-takeover"
 .br
 Any
 .I mdmon