I have a weekly parity check run on my server, 4.7, Monday mornings at 2:00 am. Normally, seems to run fine. I get home in the evening, check the web interface and it says 0 errors, like it is now.

 

#!/bin/sh
crontab -l >/tmp/crontab
grep -q "/root/mdcmd check" /tmp/crontab 1>/dev/null 2>&1
if [ "$?" = "1" ]
then
    echo "# check parity every Sun at 1 am:" >>/tmp/crontab
    echo "0 2 * * 1 /root/mdcmd check NOCORRECT 1>/dev/null 2>&1" >>/tmp/crontab
    cp /tmp/crontab /var/spool/cron/crontabs/root-
    crontab /tmp/crontab
fi

 

But, I am running a tail command and noticed this from when it ran this morning:

 

Apr 18 02:00:01 Tower kernel: mdcmd (28): check NOCORRECT
Apr 18 02:00:01 Tower kernel:
Apr 18 02:00:01 Tower kernel: md: recovery thread woken up ...
Apr 18 02:00:01 Tower kernel: md: recovery thread checking parity...
Apr 18 02:00:01 Tower kernel: md: using 1152k window, over a total of 1953514552
blocks.
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777304
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777312
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777320
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777328
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777336
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777344
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777352
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777360
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777368
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777376
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777384
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777392
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777400
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777408
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777416
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777424
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777432
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777440
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777448
Apr 18 02:39:54 Tower kernel: md: parity incorrect: 419777456

 

Just wondering why it says there "parity incorrect" while on the webui it says zero errors?

 

Thanks!

Shawn

 

Attached syslog as well...

notepad.txt

When there are messages in the system log indicating "parity incorrect" there should also be a corresponding sync error count show up as well, both during the parity check process and at the end when it displays the count from the last check.  I can't reproduce the behavior you are seeing - can you make it happen again?

Nope. Seemed to be a one time thing. Re-ran the parity check and the webui updated appropriately, showing the error count.

 

Shawn