Topic: mismatch_cnt is not 0 on /dev/md1

[bloodshoteye]

Hi,

Although this occurred on an SME8beta6 installation, it probably relates
to hardware.

Question: Does the following indicate possible drive failure in the near
future?

Firstly, The two drives were definitely in sync and ok on Friday.
Then, on Saturday cron reported the following, and in this order:

a) A RebuildFinished event has been detected on md device /dev/md1.
b) Device mismatches found: 128 is now an active member of md device /dev/md1.
c) /etc/cron.weekly/99-raid-check:
    WARNING: mismatch_cnt is not 0 on /dev/md1

A search of these forums for mismatch_cnt produced no response.

Secondly, on Sunday cat /proc/mdstat shows:

Personalities : [raid1]
md1 : active raid1 sdb1[1] sda1[0]
      104320 blocks [2/2] [UU]

md2 : active raid1 sdb2[1] sda2[0]
      732467520 blocks [2/2] [UU]

nused devices: <none>

The two drive are ok - for now?

Cheers,

[Stefano]

please don't report problems here..

raise a bug and report here the reference for future readers, thank you

[bloodshoteye]

please don't report problems here..

raise a bug and report here the reference for future readers, thank you

Ok, done. Here's the link to Bug 6562 http://bugs.contribs.org/show_bug.cgi?id=6562

EDIT: It seems this topic is under discussion at the CentOS forum. Look at comment 19: https://www.centos.org/modules/newbb/viewtopic.php?topic_id=23164

[eastend99]

See also bug http://bugs.contribs.org/show_bug.cgi?id=6160.