What to do when repair does not fix mismatch_cnt to 0 (2.6.25.1)?

[Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>]

p34:~# cat /sys/block/md3/md/mismatch_cnt
256

p34:~# echo repair > /sys/block/md3/md/sync_action

.. wait awhile ..

md3 : active raid5 sdl1[9] sdk1[8] sdj1[7] sdi1[6] sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1] sdc1[0]
      1318680576 blocks level 5, 1024k chunk, algorithm 2 [10/10] [UUUUUUUUUU]
      [=================>...]  resync = 85.0% (124634296/146520064) finish=7.9min speed=46113K/sec

.. done ..

md3 : active raid5 sdl1[9] sdk1[8] sdj1[7] sdi1[6] sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1] sdc1[0]
      1318680576 blocks level 5, 1024k chunk, algorithm 2 [10/10] [UUUUUUUUUU]

now check again:

p34:~# cat /sys/block/md3/md/mismatch_cnt
256
p34:~#

# uname -r
2.6.25.1

Usually a reboot will take care of it but I would like to know the root 
cause of it and why repair does not fix it?


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html