From: Michael Tokarev <mjt@tls.msk.ru>
To: Jason Rainforest <l3mming@iinet.net.au>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Eyal Lebedinsky <eyal@eyal.emu.id.au>,
linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: nonzero mismatch_cnt with no earlier error
Date: Sat, 24 Feb 2007 14:09:53 +0300 [thread overview]
Message-ID: <45E01D01.4080205@tls.msk.ru> (raw)
In-Reply-To: <1172310529.4431.9.camel@merlin>
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
next prev parent reply other threads:[~2007-02-24 11:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-24 0:23 nonzero mismatch_cnt with no earlier error Eyal Lebedinsky
2007-02-24 0:30 ` Justin Piszcz
2007-02-24 0:59 ` Eyal Lebedinsky
2007-02-26 4:36 ` Neil Brown
2007-02-26 5:46 ` Jeff Breidenbach
2007-02-26 8:18 ` Eyal Lebedinsky
2007-03-05 4:00 ` Tejun Heo
2007-03-05 7:52 ` Eyal Lebedinsky
2007-03-05 16:00 ` Tejun Heo
2007-03-05 22:01 ` Eyal Lebedinsky
2007-03-09 12:36 ` Tejun Heo
2007-02-24 6:58 ` Eyal Lebedinsky
2007-02-24 9:14 ` Justin Piszcz
2007-02-24 9:37 ` Justin Piszcz
2007-02-24 9:48 ` Jason Rainforest
2007-02-24 9:50 ` Justin Piszcz
2007-02-24 9:59 ` Jason Rainforest
2007-02-24 10:01 ` Justin Piszcz
2007-02-24 11:09 ` Michael Tokarev [this message]
2007-02-24 11:12 ` Justin Piszcz
2007-02-25 20:02 ` Bill Davidsen
2007-02-25 18:33 ` Frank van Maarseveen
2007-02-25 19:58 ` Christian Pernegger
2007-02-25 21:07 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E01D01.4080205@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=eyal@eyal.emu.id.au \
--cc=jpiszcz@lucidpixels.com \
--cc=l3mming@iinet.net.au \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.