FM / mdadm

/usr/share/doc/mdadm

Name	Size	Mode	Actions
examples/	-	0755	rm
ANNOUNCE-3.0	3486	0644	edit dl rm
ANNOUNCE-3.0.1	620	0644	edit dl rm
ANNOUNCE-3.0.2	583	0644	edit dl rm
ANNOUNCE-3.0.3	1009	0644	edit dl rm
ANNOUNCE-3.1	1164	0644	edit dl rm
ANNOUNCE-3.1.1	1442	0644	edit dl rm
ANNOUNCE-3.1.2	1795	0644	edit dl rm
ANNOUNCE-3.1.3	1933	0644	edit dl rm
ANNOUNCE-3.1.4	1332	0644	edit dl rm
ANNOUNCE-3.1.5	1792	0644	edit dl rm
ANNOUNCE-3.2	3014	0644	edit dl rm
ANNOUNCE-3.2.1	3313	0644	edit dl rm
ANNOUNCE-3.2.2	1546	0644	edit dl rm
ANNOUNCE-3.2.3	810	0644	edit dl rm
ANNOUNCE-3.2.4.gz	3696	0644	edit dl rm
ANNOUNCE-3.2.5	1046	0644	edit dl rm
ANNOUNCE-3.2.6	2664	0644	edit dl rm
ANNOUNCE-3.3	2752	0644	edit dl rm
ANNOUNCE-3.3.1	826	0644	edit dl rm
ANNOUNCE-3.3.2	467	0644	edit dl rm
ANNOUNCE-3.3.3	577	0644	edit dl rm
ANNOUNCE-3.3.4	1518	0644	edit dl rm
ANNOUNCE-3.4	888	0644	edit dl rm
ANNOUNCE-4.0	852	0644	edit dl rm
ANNOUNCE-4.1	551	0644	edit dl rm
ANNOUNCE-4.2	716	0644	edit dl rm
changelog.Debian.gz	2370	0644	edit dl rm
copyright	874	0644	edit dl rm
external-reshape-design.txt.gz	4933	0644	edit dl rm
FAQ.gz	11242	0644	edit dl rm
mdmon-design.txt.gz	2561	0644	edit dl rm
NEWS.Debian.gz	2172	0644	edit dl rm
README.checkarray	1667	0644	edit dl rm
README.recipes.gz	1977	0644	edit dl rm
TODO.Debian	1238	0644	edit dl rm
TODO.gz	3097	0644	edit dl rm

Edit: /usr/share/doc/mdadm/README.checkarray (1667B)

checkarray notes
================

checkarray will run parity checks across all your redundant arrays. By
default, it is configured to run on the first Sunday of each month, at 01:06
in the morning. This is realised by asking cron to wake up every Sunday with
/etc/cron.d/mdadm, but then only running the script when the day of the month
is less than or equal to 7. See #380425.

Cron will try to run the check at "idle I/O priority" (see ionice(1)), so that
the check does not overload the system too much. Note that this will only
work if all the component devices of the array employ the (default) "cfq" I/O
scheduler. See the kernel documentation[0] for information on how to verify
and modify the scheduler. checkarray does not verify this for you.

0. http://www.kernel.org/doc/Documentation/block/switching-sched.txt

If you manually invoke checkarray, it runs with default I/O priority. Should
you need to run a check at a higher (or lower) I/O priority, then have a look
at the --idle, --slow, --fast, and --realtime options.

'check' is a read-only operation, even though the kernel logs may suggest
otherwise (e.g. /proc/mdstat and several kernel messages will mention
"resync"). Please also see question 21 of the FAQ.

If, however, while reading, a read error occurs, the check will trigger the
normal response to read errors which is to generate the 'correct' data and try
to write that out - so it is possible that a 'check' will trigger a write.
However in the absence of read errors it is read-only.

You can cancel a running array check with the -x option to checkarray.

-- martin f. krafft <madduck@debian.org>  Thu, 02 Sep 2010 10:27:29 +0200

cmd: