high mismatch count after scrub

high mismatch count after scrub

[Dexter Filmore]

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?


-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.stop1984.com
http://www.againsttcpa.com

Re: high mismatch count after scrub

[Neil Brown]

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

Re: high mismatch count after scrub

[Dexter Filmore]

> > xerxes:/sys/block/md0/md# cat mismatch_cnt
> > 147248
> > Need to worry?
>
> If you have a swap file on this array, then that could explain it, so
> don't worry.

Nope, swap is not on the array.
Couple of loops tho.

>
> If not... maybe worry?
>
> I assume you did a 'check' or 'repair' before looking at this file?

Correct, "check".

> 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....

Array has been in use for quite a while.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.stop1984.com
http://www.againsttcpa.com

Re: high mismatch count after scrub

[Justin Piszcz]

On Tue, 6 Mar 2007, Dexter Filmore wrote:

>>> xerxes:/sys/block/md0/md# cat mismatch_cnt
>>> 147248
>>> Need to worry?
>>
>> If you have a swap file on this array, then that could explain it, so
>> don't worry.
>
> Nope, swap is not on the array.
> Couple of loops tho.
>
>>
>> If not... maybe worry?
>>
>> I assume you did a 'check' or 'repair' before looking at this file?
>
> Correct, "check".
>
>> 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....
>
> Array has been in use for quite a while.
>
> -- 
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
> w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
> b++(+++) DI+++ D- G++ e* h>++ r* y?
> ------END GEEK CODE BLOCK------
>
> http://www.stop1984.com
> http://www.againsttcpa.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Neil,

So in his case, is there anyway to determine which files are potentially 
corrupted?

Justin.

Re: high mismatch count after scrub

[Dexter Filmore]

> Neil,
>
> So in his case, is there anyway to determine which files are potentially
> corrupted?

I'd like to know that, too...

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------

http://www.stop1984.com
http://www.againsttcpa.com