From: Daniel Brahneborg <daniel.com@wtnord.net>
To: Daniel Brahneborg <daniel.com@wtnord.net>,
Neil Brown <neilb@cse.unsw.edu.au>,
mingo@redhat.com, linux-raid@vger.kernel.org
Subject: Re: BUG: Data corruption on Raid5 in Linux 2.6.0
Date: Mon, 29 Dec 2003 13:19:12 +0100 [thread overview]
Message-ID: <20031229131912.C9872@nettis.grimsta> (raw)
In-Reply-To: <20031229000227.GC1882@matchmail.com>; from mfedyk@matchmail.com on Sun, Dec 28, 2003 at 04:02:27PM -0800
On Sun, Dec 28, 2003 at 04:02:27PM -0800, Mike Fedyk wrote:
> On Sun, Dec 28, 2003 at 09:17:22AM +0100, Daniel Brahneborg wrote:
> > I get the same problem without it, just a few more "dma_intr:
> > DriveReady SeekComplete Error" in the syslog.
>
> You are having hard drive problems.
Perhaps... But it doesn't explain my raid5 problems.
> o check your cables
> o check your drives with smartmontools
I've run the "short" test on all four disks now, and got no
errors.
I've also done my "cp /tmp/a b ; md5sum /tmp/a b" where /tmp/a
is a 500Mb file with random data on filesystems on the individual
partitions on the four drives. That works fine every time.
Doing the same on the raid5 device on the same drives fails every
time if the file is large enough (more than say 100 MB). I also
don't get any kind of warnings in the syslog when accessing the
raid5 device.
Just to make sure, I used the same 5GB partitions for both tests,
and when a partition is used by itself it works fine. When the
same partition is used in a raid5 setup, I get corrupted files.
I've tested all four drives.
/Basic
next prev parent reply other threads:[~2003-12-29 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 23:00 BUG: Data corruption on Raid5 in Linux 2.6.0 Daniel Brahneborg
2003-12-28 5:47 ` Neil Brown
2003-12-28 8:17 ` Daniel Brahneborg
2003-12-29 0:02 ` Mike Fedyk
2003-12-29 12:19 ` Daniel Brahneborg [this message]
2003-12-28 15:00 ` Daniel Brahneborg
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=20031229131912.C9872@nettis.grimsta \
--to=daniel.com@wtnord.net \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.