Chris Adams wrote : > 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. [...]
Yes, RAID-1. So I'm assuming this is normal, since smartctl is reporting all disks as being fine. I'll see if I can backport the recent Fedora cron job to my RHEL systems if what it does is indeed just ignore the mismatch on RAID-1. Thanks for the pointer ;-) Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora release 14 (Laughlin) - Linux kernel 2.6.35.10-72.fc14.x86_64 Load : 0.23 0.15 0.09 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
