From: Brad Campbell <brad@wasp.net.au>
To: Roman Mamedov <roman@rm.pp.ru>
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Debugging a strange array corruption
Date: Tue, 14 Dec 2010 17:37:53 +0800 [thread overview]
Message-ID: <4D073AF1.7090709@wasp.net.au> (raw)
In-Reply-To: <20101214142246.20c927e1@natsu>
On 14/12/10 17:22, Roman Mamedov wrote:
> On Tue, 14 Dec 2010 16:10:07 +0800
> Brad Campbell<brad@wasp.net.au> wrote:
>
>> The drives are all on separate channels. 8 are on a pair of Marvell 88SX7042
>> controllers and 2 are on a SIL3132. This has occurred since I upgraded the
>> mainboard (and kernel at the same time - nothing like throwing more
>> variables in the mix) and its effects were subtle enough that I missed them
>> until it had successfully rotated out all of my good backups with broken
>> data. Lesson learned.
>
> I'd suggest that you try moving two disks away from SiI3132, change your
> setup so that at most ONE port on that controller is used, or none at all.
>
> Some time ago there was a report of data corruption with controllers using
> that chip when both ports simultaneously read at full speed:
> http://forum.ixbt.com/topic.cgi?id=11:35147:1200#1200 (in Russian)
> Perhaps problem not in the chip itself, but in some variations of
> schematics/components/soldering, because only two of five supposedly identical
> boards the reporter bought were corrupting data in that way, one much
> more often than the other.
>
And in the prior incarnation I was only using 1 port on that controller so the problem would never
have manifested itself. Thanks, at least I have something to try.
Regards,
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next prev parent reply other threads:[~2010-12-14 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 8:10 Debugging a strange array corruption Brad Campbell
2010-12-14 9:22 ` Roman Mamedov
2010-12-14 9:37 ` Brad Campbell [this message]
2010-12-14 9:42 ` Roman Mamedov
2010-12-14 10:29 ` Brad Campbell
2010-12-14 11:59 ` David W.
2010-12-14 12:07 ` Roman Mamedov
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=4D073AF1.7090709@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-raid@vger.kernel.org \
--cc=roman@rm.pp.ru \
/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).