From: 7091@blargh.com
To: 7091@blargh.com
Cc: Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Tue, 03 Jul 2007 20:22:00 -0700 [thread overview]
Message-ID: <courier.468B1258.000018F4@blargh.com> (raw)
In-Reply-To: <courier.468B005A.0000127A@blargh.com>
7091@blargh.com writes:
> Tejun Heo writes:
>
>> Sounds awfully similar to the recent nvidia data corruption issue. It
>> was involving the IOMMU and one of the workarounds was not using IOMMU,
>> IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
>> off by passing "iommu=off" as kernel parameter.
>>
>> --
>> tejun
>
> Blast. I stand corrected - it didn't fix it.
>
> I now have 3 300G drives hanging off the add-in card, sda sdb sdc. I did
> the following:
>
> # Make a RAID5 array of 3 out of the 4 drives I'll eventually be using
> mdadm --create /dev/md6 --chunk=64 --level=raid5 --raid-devices=4
> /dev/sda1 /dev/sdb1 /dev/sdc1 missing
Here's an odd data point.
I just broke that array, formatted all three of those partitions seperately,
mounted and did my ISO copy test.
All three drives, run one at a time, function fine. No corruption.
next prev parent reply other threads:[~2007-07-04 3:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 6:42 sata_sil, writing bug with multiple cards? 7091
2007-07-03 8:51 ` Tejun Heo
2007-07-04 1:40 ` 7091
2007-07-04 1:48 ` Tejun Heo
2007-07-04 2:05 ` 7091
2007-07-04 3:22 ` 7091 [this message]
2007-07-04 3:44 ` 7091
2007-07-04 3:53 ` Tejun Heo
2007-07-04 7:08 ` Andi Kleen
2007-07-04 8:17 ` 7091
2007-07-04 8:38 ` Andi Kleen
2007-07-04 8:52 ` Tejun Heo
2007-07-10 10:55 ` Tejun Heo
2007-07-12 3:21 ` 7091
2007-07-04 3:41 ` Tejun Heo
2007-07-04 9:18 ` Alan Cox
2007-07-04 9:14 ` Tejun Heo
2007-07-04 9:26 ` 7091
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=courier.468B1258.000018F4@blargh.com \
--to=7091@blargh.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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).