On Thu, 2009-10-29 at 14:57 +0000, Bob McElrath wrote:
> I have seen problems like this with large files on multiple fs's and
> ultimately it was a RAM problem. Scott, can you run memtester and/or
> memtest86 at bootup to verify that you don't have bad RAM? Is your CPU
> overclocked? CPU errors can also be detected with burn* programs
> (cpuburn package). A rare RAM problem can cause bitflips that you
> wouldn't notice except in large files.
>
Running memtest was one of the first things I did ;-) Likewise I
performed a read/write test of the drive and it was fine
Scott
--
Scott James Remnant
<email address hidden>
On Thu, 2009-10-29 at 14:57 +0000, Bob McElrath wrote:
> I have seen problems like this with large files on multiple fs's and
> ultimately it was a RAM problem. Scott, can you run memtester and/or
> memtest86 at bootup to verify that you don't have bad RAM? Is your CPU
> overclocked? CPU errors can also be detected with burn* programs
> (cpuburn package). A rare RAM problem can cause bitflips that you
> wouldn't notice except in large files.
>
Running memtest was one of the first things I did ;-) Likewise I
performed a read/write test of the drive and it was fine
Scott
--
Scott James Remnant
<email address hidden>