From: Markus Falb <wnefal@xxxxxxxxx>
> I do not know exactly about md's raid 6, but I always thougt that this false
> positive mismatch count thing was raid 1 specific.
> Because of this all I also would tend to turn off the weekly raid check cronjob
> for md raid 1
Ok, so basicaly we should just ignore these mismatches...
>> And mdraid seems not alarmed about it...
>> 1. Is there something to activate to get some kind of mdraid warnings?
>> In /var/log/messages I cannot find any alarming message.
>
> $ chkconfig --list mdmonitor
Already running...
> configure it with a working email address.
> And there *are* entries in /var/log/messages. Could it be that this happened a
> long time ago, you did not notice and the log files rotated out?
There are entries... but nothing alarming...
By example:
kernel: md: syncing RAID array md5
kernel: md: md5: sync done.
While mdstat says that this raid device has only 1 partition left...
md5 : active raid1 sda7[0]
4096448 blocks [2/1] [U_]
I wonder what it did sync it with...
Same for the raid devices that have a failed partition...
kernel: md: syncing RAID array md6
kernel: md: md6: sync done.
Maybe I missed a some messages a few weeks/months/years ago... but I would
expect the warnings to come back!
Anyway, I made a monitoring script that does the checks.
Thx,
JD
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
