From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: nonzero mismatch_cnt with no earlier error Date: Sat, 24 Feb 2007 14:09:53 +0300 Message-ID: <45E01D01.4080205@tls.msk.ru> References: <45DF859B.2050108@eyal.emu.id.au> <45DFE217.3020703@eyal.emu.id.au> <1172310529.4431.9.camel@merlin> Mime-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1172310529.4431.9.camel@merlin> Sender: linux-raid-owner@vger.kernel.org To: Jason Rainforest Cc: Justin Piszcz , Eyal Lebedinsky , linux-raid list List-Id: linux-raid.ids Jason Rainforest wrote: > I tried doing a check, found a mismatch_cnt of 8 (7*250Gb SW RAID5, > multiple controllers on Linux 2.6.19.2, SMP x86-64 on Athlon64 X2 4200 > +). > > I then ordered a resync. The mismatch_cnt returned to 0 at the start of As pointed out later it was repair, not resync. > the resync, but around the same time that it went up to 8 with the > check, it went up to 8 in the resync. After the resync, it still is 8. I > haven't ordered a check since the resync completed. As far as I understand, repair will do the same as check does, but ALSO will try to fix the problems found. So the number in mismatch_cnt after a repair will indicate the amount of mismatches found _and fixed_ /mjt