Well, it definitely is not from checkarray, per se, since the
script completes and exits in a matter of a few milliseconds, but
something, presumably mdadm does (or at least used to) send status reports:
Subject: Backup-Server mdadm Event Notification
RebuildStarted /dev/md0
RebuildStarted /dev/md3
RebuildFinished /dev/md3
RebuildStarted /dev/md2
RebuildFinished /dev/md2
Rebuild60 /dev/md0
Rebuild80 /dev/md0
RebuildFinished /dev/md0
On 3/13/2020 11:53 AM, Brad Campbell wrote:
On 13/3/20 08:13, Leslie Rhorer wrote:
Yes, that works just fine, as does the daily email alert whenever
an array is degraded, but `checkarray --cron --all --idle` doesn't
produce an email. It starts the array verification on all the
arrays, but no status on the processes are sent.
The normal execution for the script is to submit `echo check >
/sys/block/mdx/md/sync_action` and then exit. Obviously, the rest of
the processes are handled by the scheduler and mdadm. I'm not seeing
how anything other than mdadm should be generating the status emails.
I don't get messages from checkarray.
I get them from logcheck after they get dumped in the syslog :
This email is sent by logcheck. If you no longer wish to receive
such mail, you can either deinstall the logcheck package or modify
its configuration file (/etc/logcheck/logcheck.conf).
System Events
=-=-=-=-=-=-=
Mar 1 01:09:17 srv mdadm[4471]: RebuildFinished event detected on md
device /dev/md2, component device mismatches found: 230656 (on raid
level 1)
(Lots of errors. One drive supports deterministic read after trim and
the other doesn't)
I've never really looked at it any closer than that to be honest.
Brad.
