Re: raid5 crash (possible VM problem???)

[Kristian Eide]

--nextPart1302866.K5r9HLpeFn
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> 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 rela=
ted=20
to raid5, however, I have tested the individual SATA disks without getting=
=20
any errors. This only happens when combining them into a raid5 array (other=
=20
raid levels not tested).

ReiserFS: md3: journal params: device md3, size 8192, journal first block 1=
8,=20
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=3D0, want=3D18446744063991695384, limit=3D1465175040
attempt to access beyond end of device
md3: rw=3D0, want=3D18446744062355374704, limit=3D1465175040
attempt to access beyond end of device
md3: rw=3D0, want=3D4913837584, limit=3D1465175040
attempt to access beyond end of device
md3: rw=3D0, want=3D18446744071656162744, limit=3D1465175040

I have 4 250GB SATA disk combined into one raid5 volume (kernel 2.6.10), an=
d=20
this error happens after copying a few gigabytes of data into the volume an=
d=20
then trying to read them back.

=2D-=20
Kristian

--nextPart1302866.K5r9HLpeFn
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBB6rOXRBuET7ul/ccRAgSFAJ45ZChXxUGMDpCIi/uww8HaKnxcFwCgr4FI
BDSvZwlgC0/iAGBOIVkRBAk=
=db1K
-----END PGP SIGNATURE-----

--nextPart1302866.K5r9HLpeFn--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/