From: Bas Bloemsaat <bas.bloemsaat@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: SATA_SX4: data corruption with simultaneous writes
Date: Wed, 29 Dec 2004 09:31:07 +0100 [thread overview]
Message-ID: <7c4668e5041229003166ebfc2e@mail.gmail.com> (raw)
In-Reply-To: <20041228134745.GA13912@solarsystems.de>
FWIW, we've experienced similar problems with software raid systems on
this controller.
In two machines, with 4 and 3 disks connected to the controllers, WD
Raptors, 36.7GB. Tested both ReiserFS (which I unjustly blamed at
first) and ext3. Kernels 2.6.7-2.6.9
Funny thing (or not so funny actually) was that after a while the when
/dev/md0 (sdb-c-d-e) got stressed bad enough fs corruption got worse
and even kernel panics would occur. That's strange, because the system
disk was on /dev/sda, which was not even on that controller. But this
was only when stressed, so it strikes me as related to the parent
call.
Anyway, the specs of these machines were pretty similar to
Christian's. P4 (2.8 and 3.2) on intel boards (D865GBFL I believe).
1GB mem in each machine.
I haven't been able to dive into this, as the machines are at work
and, well, working now. Without the disks on those controllers, that
is.
On Tue, 28 Dec 2004 14:47:45 +0100, Christian Vogel
<chris@solarsystems.de> wrote:
> I want to report data corruption that is happening here with a
> promise sx4 SATA controller during simultaneous writes to four connected
> disks, using kernel 2.6.9.
>
*snip*
next prev parent reply other threads:[~2004-12-29 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 13:47 SATA_SX4: data corruption with simultaneous writes Christian Vogel
2004-12-28 14:09 ` Christian Vogel
2004-12-29 8:31 ` Bas Bloemsaat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 6:34 Johny A
2005-01-09 1:35 ` Johny A
2005-02-06 12:04 ` Johny A
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=7c4668e5041229003166ebfc2e@mail.gmail.com \
--to=bas.bloemsaat@gmail.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).