> You could try this patch. It might hide the real problem, or it might > cause it to manifest in some other way.
I've applied the patch, but I now get another error; this might not be related to raid5, however, I have tested the individual SATA disks without getting any errors. This only happens when combining them into a raid5 array (other raid levels not tested). ReiserFS: md3: journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: md3: checking transaction log (md3) ReiserFS: md3: Using r5 hash to sort names attempt to access beyond end of device md3: rw=0, want=18446744063991695384, limit=1465175040 attempt to access beyond end of device md3: rw=0, want=18446744062355374704, limit=1465175040 attempt to access beyond end of device md3: rw=0, want=4913837584, limit=1465175040 attempt to access beyond end of device md3: rw=0, want=18446744071656162744, limit=1465175040 I have 4 250GB SATA disk combined into one raid5 volume (kernel 2.6.10), and this error happens after copying a few gigabytes of data into the volume and then trying to read them back. -- Kristian
pgpdSNcP7pfJ7.pgp
Description: PGP signature
