From: David R <spam.david.trap@unsolicited.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fw: [Bugme-new] [Bug 3993] New: sata_sx4 causes file corruption during simultaneous writes
Date: Wed, 05 Jan 2005 22:24:31 +0000 [thread overview]
Message-ID: <41DC691F.3010800@unsolicited.net> (raw)
In-Reply-To: <20050105133548.13ac80d3.akpm@osdl.org>
Andrew Morton wrote:
>controller, using the libata sata_sx4 driver. Individual writes to the drives
>are fine. When the drives are written to simultaneously, either by multiple cp
>threads or assembling them in a raid 5, corruption occurs as evidenced by fsck
>errors and inconsistent md5 sums.
>
>
>
FWIW at <$dayjob> we have had exactly the same issues using Win2k (ugh)
and Promise's own drivers on a Dual Opteron system (Rioworks HDAMA) with
an integrated Fastrak S150TX4 controller. Relatively stable using a
single drive as a separate volume (our application prefers a RAID 0
stripe), but random subtle corruptions when using an array (striped or
mirrored). This is both using the controller's embedded RAID and W2K's
software RAID (with the Promise configured to present separate disks).
Firmware upgrades/downgrades were tried with no luck. We have two
identically configured machines that both exhibit the same problem.
Interestingly, the errors were always single flipped bit(s) at random
offset(s) within the file. Different on each run. Sounds like a RAM
issue but both machines memtest fine and run without issues when using a
single drive.
We never found a solution (we simply use single (large) SATA drives
instead) :-(
David
prev parent reply other threads:[~2005-01-05 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 21:35 Fw: [Bugme-new] [Bug 3993] New: sata_sx4 causes file corruption during simultaneous writes Andrew Morton
2005-01-05 22:24 ` David R [this message]
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=41DC691F.3010800@unsolicited.net \
--to=spam.david.trap@unsolicited.net \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.