From: Andrew Morton <akpm@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Fw: [Bugme-new] [Bug 3993] New: sata_sx4 causes file corruption during simultaneous writes
Date: Wed, 5 Jan 2005 13:35:48 -0800 [thread overview]
Message-ID: <20050105133548.13ac80d3.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Wed, 5 Jan 2005 08:08:32 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3993] New: sata_sx4 causes file corruption during simultaneous writes
http://bugme.osdl.org/show_bug.cgi?id=3993
Summary: sata_sx4 causes file corruption during simultaneous
writes
Kernel Version: 2.6.9
Status: NEW
Severity: normal
Owner: andmike@us.ibm.com
Submitter: sam@davidoffdotnet.net
Distribution: Debian testing (sarge)
Hardware Environment: Dual Pentium III 733 Mhz, 512 MB ECC Ram, Promise SX4 S150
Controller
Software Environment: 2.6.9 kernel with SMP support
Problem Description:
Three Seagate 160MB drives connected to the Promise SX4 S150 'Fasttrak'
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.
No hardware errors are reported. The drives all give clean badblocks tests and
return good benchmarks via bonnie++.
The system used has passed rigorous mprime testing and memtest testing. The ram
used in the promise card has passed promises's test, is certified as promise
compatible, and has passed indepndent memtest testing when installed in a
separate system.
Steps to reproduce:
1. Format drives and setup filesystem.
2. Start simultaneous instances of cp, copying large files to each drive.
3. Compare md5sums of copied files OR run fsck
Alternative:
1. Assemble drives into raid 5 array
2. copy file
3. compare md5 of copied file with original OR run fsck
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-01-05 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 21:35 Andrew Morton [this message]
2005-01-05 22:24 ` Fw: [Bugme-new] [Bug 3993] New: sata_sx4 causes file corruption during simultaneous writes David R
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=20050105133548.13ac80d3.akpm@osdl.org \
--to=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.