On Wed, Jan 07, 2004 at 02:42:49PM -0800, Mike Fedyk wrote:
> On Wed, Jan 07, 2004 at 01:31:11PM -0800, Steven Ihde wrote:
> > On Wed, Jan 07, 2004 at 01:08:16PM -0800, Mike Fedyk wrote:
> > > Can you find the version of 2.6.0-test where this started?
> >
> > This is a relatively new raid5 array -- I've been having this problem
> > ever since I created the array, which was sometime after I switched to
> > the 2.6.0-test series. So I'm not claiming there is (or isn't) a
> > version of 2.6.0-test that works -- only that 2.6.0-test* and 2.6.0
> > are the only versions I've tried, and that's where I've seen the
> > problem.
>
> Then please verify it on a 2.4.24 kernel, or run some hardware tests.
>
> o Memtest86 (running all tests with at least one pass (this can take 24
> hours for one pass depending on how much memory you have...)
> o burn{BX,MMX,etc}
I've run the full memtest86 within the past couple months and it came
out OK (I bought a bad stick of RAM at some point and wanted to be
sure the replacement was good).
If noone has any suggestions other than to try 2.4.24, I'll give it a
try and report back in a couple weeks (it'll take that long to be sure
since this problem sometimes doesn't occur for 10-15 days at a time).
Thanks,
Steve
-
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
