linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: linux-raid list <linux-raid@vger.kernel.org>
Subject: Re: nonzero mismatch_cnt with no earlier error
Date: Sat, 24 Feb 2007 17:58:31 +1100	[thread overview]
Message-ID: <45DFE217.3020703@eyal.emu.id.au> (raw)
In-Reply-To: <45DF859B.2050108@eyal.emu.id.au>

I did a resync since, which ended up with the same mismatch_cnt of 184.
I noticed that the count *was* reset to zero when the resync started,
but ended up with 184 (same as after the check).

I thought that the resync just calculates fresh parity and does not
bother checking if it is different. So what does this final count mean?

This leads me to ask: why bother doing a check if I will always run
a resync after an error - better run a resync in the first place?

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
	attach .zip as .dat

  parent reply	other threads:[~2007-02-24  6:58 UTC|newest]

Thread overview: 20+ 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-02-24  6:58 ` Eyal Lebedinsky [this message]
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
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=45DFE217.3020703@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).