From: Jim Paris <jim@jtan.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Silent corruption on AMD64
Date: Sat, 31 Mar 2007 20:03:16 -0700 [thread overview]
Message-ID: <20070401030315.GA24080@jim.sh> (raw)
In-Reply-To: <20070401012736.GT15189@vitelus.com>
Aaron Lehmann wrote:
> I discovered a reproducible way of causing silent file corruption.
...
> 1. Heavy Ethernet load (nc remotehost < /dev/zero)
> 2. Heavy disk write load on any non-sata_sil drive (cat /dev/zero > /path)
> 3. Heavy disk read load on any other drive (tar c /path | cat > /dev/null)
Since it shows up under heavy load that includes unrelated devices, I
think ruling out hardware problems is important. Some suggestions:
- Use mcelog to see if you're getting any machine check exceptions
that would indicate hardware error: http://freshmeat.net/projects/mcelog/
- Use the edac module to turn on pci parity and memory error checks:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/drivers/edac/edac.txt
- Run memtest86+ for several loops to make sure your RAM is ok
- Try moving the SiI card to a different slot
- Try running the SATA drives from a separate power supply
- Move disks and cables around to see whether the problem follows the
disks, the cables, or the controllers
- Try enabling the "spread spectrum" clock option in your BIOS to
reduce EMI
-jim
next prev parent reply other threads:[~2007-04-01 3:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 1:27 Silent corruption on AMD64 Aaron Lehmann
2007-04-01 2:52 ` Andrew Morton
2007-04-01 3:20 ` Aaron Lehmann
2007-04-01 3:03 ` Jim Paris [this message]
2007-04-01 4:39 ` Aaron Lehmann
2007-04-01 13:58 ` Andi Kleen
2007-04-04 18:45 ` Silent corruption with r8169 Francois Romieu
2007-04-04 20:06 ` Aaron Lehmann
2007-04-04 20:45 ` Francois Romieu
2007-04-05 11:41 ` Andi Kleen
2007-04-02 13:30 ` Silent corruption on AMD64 Stuart MacDonald
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=20070401030315.GA24080@jim.sh \
--to=jim@jtan.com \
--cc=aaronl@vitelus.com \
--cc=linux-ide@vger.kernel.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 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).