From: Kristian Eide <kreide@online.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: raid5 crash (possible VM problem???)
Date: Sun, 16 Jan 2005 19:33:56 +0100 [thread overview]
Message-ID: <200501161933.59701.kreide@online.no> (raw)
In-Reply-To: <16857.54682.183762.561368@cse.unsw.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
> 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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-16 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 22:04 raid5 crash Kristian Eide
2004-12-22 22:26 ` Norbert van Nobelen
2004-12-22 23:05 ` Kristian Eide
2004-12-22 23:08 ` Neil Brown
2004-12-23 9:51 ` Prakash K. Cheemplavam
2004-12-23 19:45 ` Kristian Eide
2005-01-03 23:30 ` raid5 crash (possible VM problem???) Neil Brown
2005-01-16 18:33 ` Kristian Eide [this message]
2005-01-13 14:58 ` raid5 crash Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501161933.59701.kreide@online.no \
--to=kreide@online.no \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome