From: Ville Herva <vherva@niksula.hut.fi>
To: linux-kernel@vger.kernel.org
Cc: Jani Forssell <jani.forssell@viasys.com>,
thockin@sun.com, andre@linux-ide.org
Subject: Re: HPT370 on 2.2.20+ide-patch - tried 2.4.15 and it fails, too
Date: Sat, 24 Nov 2001 08:52:01 +0200 [thread overview]
Message-ID: <20011124085201.G4809@niksula.cs.hut.fi> (raw)
In-Reply-To: <2173081930.1006455144@[195.224.237.69]> <20011122210503.B4809@niksula.cs.hut.fi> <20011122215424.C4809@niksula.cs.hut.fi> <20011123143502.D4809@niksula.cs.hut.fi> <20011123163932.E4809@niksula.cs.hut.fi> <20011123233211.F4809@niksula.cs.hut.fi>
In-Reply-To: <20011123233211.F4809@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Fri, Nov 23, 2001 at 11:32:11PM +0200
On Fri, Nov 23, 2001 at 11:32:11PM +0200, you [Ville Herva] claimed:
>
> Ok, it isn't raid. It took a little more effort to reproduce with plain
> /dev/hd[eg] read, but the md5sum mismatch eventually happaned.
>
> This was with 2.2.20+IDE, no hpt patch. The drives were forced to UDMA33 as
> opposed to (default) UDMA66. This time, nothing shows up in the log.
>
> I'll try again with 2.2.18pre19 (this time harder) to make sure it really
> _really_ doesn't happen with it.
(I ahven't gotten around to try this, but...)
> Then I'll give 2.4.15 a shot to see if hpt behaves (2.4 lacks e2compr
> however, so I'm not sure I can actually use it).
...I compiled 2.4.15 + Tim Hockin's HPT370 patch. I let it run the test over
night, but
dd if=/dev/md0 bs=1048576 skip=65536 count=1024 | md5sum
had stalled at _second_ run. The first, identical run had gone through.
The point where it happened is after dd has read the last (not whole GB) and
is trying to skip slightly more than the size of md0:
At 63 GB
756+1 records in
756+1 records out
b1a566b4b54905ab21d138670b7abae3 -
At 64 GB
<stalls>
This never happened with 2.2.*
What's more, the md5sum of 1st and 2nd run differ at 31GB:
@@ -125,7 +125,7 @@
At 31 GB
1024+0 records in
1024+0 records out
-c137bbbc546b03b54188697db0758143 -
+0bee73556a9fbb38d3af79b0d11b18ec -
At 32 GB
1024+0 records in
1024+0 records out
There's two BadCRC errors in the log:
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }
Bleah. I'll try 2.4.15 vanilla (no hpt patch) and UDMA33 (instead of UDMA66)
next.
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-11-24 6:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 18:52 What are the recommended software RAID patch(es) for 2.2.20? Alex Bligh - linux-kernel
2001-11-22 19:05 ` Ville Herva
2001-11-22 19:54 ` Ville Herva
2001-11-23 12:35 ` HPT370 on 2.2.20+ide-patch Ville Herva
2001-11-23 14:39 ` HPT370 on 2.2.20+ide-patch - or is it RAID? Ville Herva
2001-11-23 21:32 ` Ville Herva
2001-11-24 6:52 ` Ville Herva [this message]
2001-11-24 7:17 ` HPT370 on 2.2.20+ide-patch - tried 2.4.15 and it fails, too Ville Herva
2001-11-25 14:06 ` HPT370 + IBM-DPTA-373420 corrupt data on 2.2 _and_ 2.4 Ville Herva
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=20011124085201.G4809@niksula.cs.hut.fi \
--to=vherva@niksula.hut.fi \
--cc=andre@linux-ide.org \
--cc=jani.forssell@viasys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
/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
all inboxes | Powered by JetHome®