--- On Fri, 29/1/10, Goswin von Brederlow <goswin-v-b@xxxxxx> wrote: > From: Goswin von Brederlow <goswin-v-b@xxxxxx> > Subject: Re: Why does one get mismatches? > To: Jon@xxxxxxxxxxxxxxx > Cc: linux-raid@xxxxxxxxxxxxxxx > Date: Friday, 29 January, 2010, 23:52 > Jon Hardcastle <jd_hardcastle@xxxxxxxxx> > writes: > > > --- On Thu, 28/1/10, Goswin von Brederlow <goswin-v-b@xxxxxx> > wrote: > > > >> From: Goswin von Brederlow <goswin-v-b@xxxxxx> > >> Subject: Re: Why does one get mismatches? > >> To: linux-raid@xxxxxxxxxxxxxxx > >> Date: Thursday, 28 January, 2010, 20:24 > >> "Tirumala Reddy Marri" <tmarri@xxxxxxxx> > >> writes: > >> > >> > I just tried and miss-match count is zero. > >> Interesting, is XOR engine > >> > doing something wrong ? . Then I ran a test > where I > >> raw-write the file > >> > to /dev/md0. Then did the raw-read for the > same size. > >> In this case XOR > >> > matched as expected. Then I failed a drive > using > >> "mdadm -f /dev/md0 > >> > /dev/sda". Then I read the same size data > again from > >> /dev/md0. And > >> > checksum matches too. > >> > What is this mean XOR engine is doing right > thing. But > >> "chec/repair" > >> > test is not functioning properly with > XOR-engine ? > >> > > >> > Or is this something to do with how the > buffers > >> are handled ? may they > >> > are cached ? > >> > > >> > > >> > -Marri > >> > >> No idea. But if everything works without the XOR > engine and > >> gives > >> mismatches with then I would think there is a > software or > >> hardware error > >> there and not in the cable or disks. > >> > >> MfG > >> Goswin > >> -- > >> To unsubscribe from this list: send the line > "unsubscribe > >> linux-raid" in > >> the body of a message to majordomo@xxxxxxxxxxxxxxx > >> 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 > > > > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
