From: Johny A <kernel@agotnes.com>
To: linux-ide@vger.kernel.org
Cc: jgarzik@pobox.com
Subject: Re: SATA_SX4: data corruption with simultaneous writes
Date: Thu, 30 Dec 2004 16:34:04 +1000 [thread overview]
Message-ID: <41D3A15C.5050809@agotnes.com> (raw)
Jeff et al,
I found this one on the mailing-list;
http://marc.theaimsgroup.com/?l=linux-ide&m=109749133709795&w=2
and have the same issues as described there, and also in the previous
mails in this thread.
The difference is, I can reproduce this with the simplest possible setup;
I have an older Asus Mobo with an AMD1.33GHz CPU,
1 Promise SX4 SATA controller (0000:00:0a.0 RAID bus controller: Promise
Technology, Inc.: Unknown device 6622 (rev 01))
2 Seagate ST380817AS, Rev: 3.42 (80 GB SATA) disks
Disks each have 1 large partition with ext2 on them.
1. I boot off a Gentoo LiveCD running 2.6.9
2. I scp over some 180 MB simultaneously to the two disks across the
network, one shell copying to 1 disk only
3. Unzip the .bz2 and .gz files just copied the files, again 1 shell
working on each disk (no cross disk stuff going on at all).
Typically, within a few minutes at most of the unzipping starting I get
CRC errors on the files. No errors in dmesg necessarily. Sometimes I get
errors unzipping - unmount the drive and run fsck which reports no
errors - very insidious!
I'd like the card to work - hey, I got one! and am willing to use my
setup for testing of new driver versions. I'm useful with C, but not a
kernel hacker, give me pointers to what needs done and I'll get it done,
no worries...
Let me know if I can help getting this thing fixed!
Thanks,
Johny A
next reply other threads:[~2004-12-30 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 6:34 Johny A [this message]
2005-01-09 1:35 ` SATA_SX4: data corruption with simultaneous writes Johny A
2005-02-06 12:04 ` Johny A
-- strict thread matches above, loose matches on Subject: below --
2004-12-28 13:47 Christian Vogel
2004-12-28 14:09 ` Christian Vogel
2004-12-29 8:31 ` Bas Bloemsaat
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=41D3A15C.5050809@agotnes.com \
--to=kernel@agotnes.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).