mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ville Herva <vherva@niksula.hut.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: HPT370 on 2.2.20+ide-patch - or is it RAID?
Date: Fri, 23 Nov 2001 23:32:11 +0200	[thread overview]
Message-ID: <20011123233211.F4809@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>
In-Reply-To: <20011123163932.E4809@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Fri, Nov 23, 2001 at 04:39:32PM +0200

On Fri, Nov 23, 2001 at 04:39:32PM +0200, you [Ville Herva] claimed:
> On Fri, Nov 23, 2001 at 02:35:02PM +0200, you [Ville Herva] claimed:
> > On Thu, Nov 22, 2001 at 09:54:24PM +0200, you [Ville Herva] claimed:
> > 
> > I'm trying again with 2.2.20/IDE 05042001/no hpt patch/slightly older
> > bios/UDMA33 instead of UDMA66. (Just _too_ many variables... Phew.)
> 
> 2.2.20/IDE 05042001/no hpt patch/UDM33 gives no IDE errors, but
> /dev/md0 md5sums still differ.
> 
> Since I didn't see the corruption with /dev/hde nor /dev/hdg, I'm beginning
> to wonder if this is in fact RAID/VM/some other problem...?
> 
> 2.2.19 included the VM rewrite, and I also patched the 2.2.20 kernel with
> Andrea's VM-locked-1 -patch (which I figure shouldn't really affect read
> path?)
> 
> The 2.2.18pre19 kernel (that works) uses 2.2.17-raid A0-patch, and
> 2.2.20 uses 2.2.19-A1. The differences between the two seems trivial.
> 
> I would be delighted if someone could confirm that 2.2.20+raid-A1 works 100%
> correct... Just md5summing the contents of /dev/md0 3-4 times should do if
> were lucky. It takes time, though...

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.

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).


-- v --

v@iki.fi

  reply	other threads:[~2001-11-23 21:32 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 [this message]
2001-11-24  6:52           ` HPT370 on 2.2.20+ide-patch - tried 2.4.15 and it fails, too Ville Herva
2001-11-24  7:17             ` 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=20011123233211.F4809@niksula.cs.hut.fi \
    --to=vherva@niksula.hut.fi \
    --cc=linux-kernel@vger.kernel.org \
    /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®