From: Edward Tandi <etandi@talk21.com>
To: linux-kernel@vger.kernel.org
Subject: HPT370 driver problems
Date: Sat, 23 Jun 2001 18:39:45 -0700 [thread overview]
Message-ID: <3B3544E1.9080801@talk21.com> (raw)
People,
I have an IWill IDE Raid card with the Highpoint HPT370 Chip. I am
running this on a Dual Processor board (800MHz PIIIs) with a Mandrake
8.0 Disrtibution (2.4.3 Kernel). 200MB of RAM and all slots filled with
lots of cards. I was glad to see that Linux auto-detected the IDE/Raid card.
The initial hardware configuration had two 40G IBM drives (7200RPM
UDMA100) each attached as the IDE Master (using cable select) of the
primary and secondary IDE interfaces as this is the optimum for two
drives. I then used the md/meta tools to stripe the two.
Then I started to migrate data. This all went well untill I decided to
check stuff with diff. Well, diff found many files to be different. I
tried all the hdparm settings to no avail. I tried reiserfs to no avail.
I tried swithching to LVM to no avail. I pulled out a processor, still
the same result (I then broke the slot1 socket trying to put it back in
-ooh my wallet hurts!). So I then focussed on looking at the type of
corruption. It's approximately 2 bytes in 300 megs -so it's probably a
dreaded off-by-one.
The real problem with this one is that it was hard to re-produce. But I
then decided to isolate the drives and found that operations on
individual drives were OK, but if you tried to use the two together,
pa-tang!
Now here's the interesting bit; I connected the two drives onto the same
cable (and therefore interface). It worked without fault. No
corruptions. So I guess the problem is at the driver level when
inter-working across the primary and secondary IDE interfaces.
Has anyone else seen this. Any patches/workarounds? -cos I want to add
another two drives. TIA,
Ed-T.
reply other threads:[~2001-06-23 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B3544E1.9080801@talk21.com \
--to=etandi@talk21.com \
--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