From: Neil Brown <neilb@suse.de>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: high mismatch count after scrub
Date: Tue, 6 Mar 2007 15:18:08 +1100 [thread overview]
Message-ID: <17900.60288.751357.807885@notabene.brown> (raw)
In-Reply-To: message from Dexter Filmore on Tuesday March 6
On Tuesday March 6, Dexter.Filmore@gmx.de wrote:
> So I practiced what I learned today and scrubbed the array.
> Getting this:
>
> xerxes:/sys/block/md0/md# cat mismatch_cnt
> 147248
>
> 4x 250GB Samsung sATA, smartctl says all fine.
>
> Need to worry?
>
If you have a swap file on this array, then that could explain it, so
don't worry.
If not... maybe worry?
I assume you did a 'check' or 'repair' before looking at this file?
If not and it is a newly created array, then it is just telling that
the drives didn't have the same content when you started....
NeilBrown
next prev parent reply other threads:[~2007-03-06 4:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 2:06 high mismatch count after scrub Dexter Filmore
2007-03-06 4:18 ` Neil Brown [this message]
2007-03-06 12:45 ` Dexter Filmore
2007-03-06 12:51 ` Justin Piszcz
2007-03-07 13:10 ` Dexter Filmore
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=17900.60288.751357.807885@notabene.brown \
--to=neilb@suse.de \
--cc=Dexter.Filmore@gmx.de \
--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).