mismatch_cnt != 0, member content mismatch, but md says the mirror is good

[Michael ODonnell]

Anybody else running CentOS5.x (or RHAT equiv?) care to share the
results from this command:

    grep -i sync /var/log/* | fgrep -i raid

It looks like the RAIDs on at least seven of our (mostly stock) CentOS5.4
systems are routinely getting broken and going through a resync operation
on a weekly basis at 4:22am which is when that /etc/cron.weekly script
runs that's generating the mismatch_cnt warnings in question.  I mightn't
have noticed this except that we have a script that periodically checks
/proc/mdstat and pops a dialog box on the X display if it appears we
don't have a healthy RAID, and I was astounded to see one on each of
those machines when I arrived this morning.  Heads up...