управлять MD-устройствами, также известными как Linux Software RAID (manage MD devices aka Linux Software RAID)
For Monitor mode:
-m, --mail
Give a mail address to send alerts to.
-p, --program, --alert
Give a program to be run whenever an event is detected.
-y, --syslog
Cause all events to be reported through 'syslog'. The
messages have facility of 'daemon' and varying priorities.
-d, --delay
Give a delay in seconds. mdadm polls the md arrays and
then waits this many seconds before polling again. The
default is 60 seconds. Since 2.6.16, there is no need to
reduce this as the kernel alerts mdadm immediately when
there is any change.
-r, --increment
Give a percentage increment. mdadm will generate
RebuildNN events with the given percentage increment.
-f, --daemonise
Tell mdadm to run as a background daemon if it decides to
monitor anything. This causes it to fork and run in the
child, and to disconnect from the terminal. The process
id of the child is written to stdout. This is useful with
--scan which will only continue monitoring if a mail
address or alert program is found in the config file.
-i, --pid-file
When mdadm is running in daemon mode, write the pid of the
daemon process to the specified file, instead of printing
it on standard output.
-1, --oneshot
Check arrays only once. This will generate NewArray
events and more significantly DegradedArray and
SparesMissing events. Running
mdadm --monitor --scan -1
from a cron script will ensure regular notification of any
degraded arrays.
-t, --test
Generate a TestMessage alert for every array found at
startup. This alert gets mailed and passed to the alert
program. This can be used for testing that alert message
do get through successfully.
--no-sharing
This inhibits the functionality for moving spares between
arrays. Only one monitoring process started with --scan
but without this flag is allowed, otherwise the two could
interfere with each other.
