Once upon a time, Matthias Saou
<th...@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net> said:
> Initially I receive a cron.weekly email about "WARNING: mismatch_cnt is
> not 0 on /dev/md2", which is why I go ahead and force a repair, then
> force a check. It gets worse after every step, and each of those two
> operations takes hours (750GB SATA disks).
RAID 1 (mirror)? This is "normal". Here's the comment from the RAID
check cron job in newer Fedora:
# Due to the fact that raid1 writes in the kernel are unbuffered,
# a raid1 array can have non-0 mismatch counts even when the
# array is healthy. These non-0 counts will only exist in
# transient data areas where they don't pose a problem. However,
# since we can't tell the difference between a non-0 count that
# is just in transient data or a non-0 count that signifies a
# real problem, simply don't check the mismatch_cnt on raid1
# devices as it's providing far too many false positives. But by
# leaving the raid1 device in the check list and performing the
# check, we still catch and correct any bad sectors there might
# be in the device.
--
Chris Adams <[email protected]>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
