--- On Fri, 29/1/10, Goswin von Brederlow <goswin-v-b@web.de> wrote:

From: Goswin von Brederlow <redacted>
Subject: Re: Why does one get mismatches?
To: Jon@eHardcastle.com
Cc: linux-raid@vger.kernel.org
Date: Friday, 29 January, 2010, 23:52
Jon Hardcastle [off-list ref]
writes:

quoted

--- On Thu, 28/1/10, Goswin von Brederlow <goswin-v-b@web.de>

wrote:

quoted

quoted

From: Goswin von Brederlow <redacted>
Subject: Re: Why does one get mismatches?
To: linux-raid@vger.kernel.org
Date: Thursday, 28 January, 2010, 20:24
"Tirumala Reddy Marri" [off-list ref]
writes:

quoted

I just tried and miss-match count is zero.

Interesting, is XOR engine

quoted

doing something wrong ? . Then I ran a test

where I

quoted

quoted

raw-write the file

quoted

to /dev/md0. Then did the raw-read for the

same size.

quoted

quoted

In this case XOR

quoted

matched as expected. Then I failed a drive

using

quoted

quoted

"mdadm -f /dev/md0

quoted

/dev/sda". Then I read the same size data

again from

quoted

quoted

/dev/md0. And

quoted

checksum matches too. 
What is this mean XOR engine is doing right

thing. But

quoted

quoted

"chec/repair"

quoted

test is not functioning properly with

XOR-engine ?

quoted

quoted

quoted

Or is this something to do with  how the

buffers

quoted

quoted

are handled ? may they

quoted

are cached ?


-Marri

No idea. But if everything works without the XOR

engine and

quoted

quoted

gives
mismatches with then I would think there is a

software or

quoted

quoted

hardware error
there and not in the cable or disks.

MfG
        Goswin
--
To unsubscribe from this list: send the line

"unsubscribe

quoted

quoted

linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

i think my RAM is fecked - does that sound like a

possible cause? memtest86 gives PAGES of red errors when run
but the POST gives nothing and the machine boots.... it has
512MB

quoted

i have some more on order as a speculative.. 

If memtest gives errors you certainly have errors. The
reverse isn't
allways true.

MfG
        Goswin

Might have been a false alarm.. both the new chip and old one in an assortment of slots give the errors - upgrade from memtest86 3.3 to 3.5 and the errors go away.


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