.\" See file COPYING in distribution for details.
-.TH MDMON 8 "" v3.2.3
+.TH MDMON 8 "" v3.3.2
.SH NAME
mdmon \- monitor MD external metadata arrays
.SH SYNOPSIS
-.BI mdmon " [--all] [--takeover] CONTAINER"
+.BI mdmon " [--all] [--takeover] [--foreground] CONTAINER"
.SH OVERVIEW
The 2.6.27 kernel brings the ability to support external metadata arrays.
External metadata formats, like DDF, differ from the native MD metadata
formats in that they define a set of disks and a series of sub-arrays
within those disks. MD metadata in comparison defines a 1:1
-relationship between a set of block devices and a raid array. For
-example to create 2 arrays at different raid levels on a single
+relationship between a set of block devices and a RAID array. For
+example to create 2 arrays at different RAID levels on a single
set of disks, MD metadata requires the disks be partitioned and then
each array can be created with a subset of those partitions. The
supported external formats perform this disk carving internally.
device to monitor. It can be a full path like /dev/md/container, or a
simple md device name like md127.
.TP
+.B \-\-foreground
+Normally,
+.I mdmon
+will fork and continue in the background. Adding this option will
+skip that step and run
+.I mdmon
+in the foreground.
+.TP
.B \-\-takeover
This instructs
.I mdmon
containers with names longer than 5 characters, this argument can be
arbitrarily extended, e.g. to
.BR \-\-all-active-arrays .
+.TP
.PP
Note that
.B .sock
file. The particular filesystem to use is given to mdmon at compile
time and defaults to
-.BR /dev/.mdadm .
+.BR /run/mdadm .
This filesystem must persist through to shutdown time.