From: 7091@blargh.com
To: Tejun Heo <htejun@gmail.com>
Cc: 7091@blargh.com, linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: sata_sil, writing bug with multiple cards?
Date: Tue, 03 Jul 2007 19:05:14 -0700 [thread overview]
Message-ID: <courier.468B005A.0000127A@blargh.com> (raw)
In-Reply-To: <468A0E24.7020000@gmail.com>
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
# Make the FS
mkfs.ext3 /dev/md6
# Test
cp KNOPPIX_V5.1.0CD-2006-12-30-EN.iso kn1.iso
cp kn1.iso kn2.iso
cp kn2.iso kn3.iso
cp kn3.iso kn4.iso
# Check
md5sum *.iso
eea5ecb53f1c6a397bcfeedc2fd42c64 kn1.iso
0360941210aa2d7159999e37c636f8cb kn2.iso
md5sum: kn3.iso: Input/output error
86b008915fe02569a513b6c5ec45a523 kn4.iso
In the dmesg:
[ 2619.483783] attempt to access beyond end of device
[ 2619.483956] md6: rw=0, want=25890291976, limit=1758201216
[ 2619.484121] attempt to access beyond end of device
[ 2619.484284] md6: rw=0, want=30654872552, limit=1758201216
[ 2619.484452] attempt to access beyond end of device
[ 2619.484614] md6: rw=0, want=33748316016, limit=1758201216
[ 2619.484780] attempt to access beyond end of device
[ 2619.484943] md6: rw=0, want=7818926368, limit=1758201216
[ 2619.485122] attempt to access beyond end of device
[ 2619.485285] md6: rw=0, want=32912340352, limit=1758201216
[ 2619.485451] attempt to access beyond end of device
[ 2619.496228] md6: rw=0, want=2277136440, limit=1758201216
[ 2619.496394] attempt to access beyond end of device
[ 2619.496557] md6: rw=0, want=2128357688, limit=1758201216
[ 2619.529625] attempt to access beyond end of device
[ 2619.530392] md6: rw=0, want=25890291976, limit=1758201216
next prev parent reply other threads:[~2007-07-04 2:05 UTC|newest]
Thread overview: 20+ 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 [this message]
2007-07-04 3:22 ` 7091
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
-- strict thread matches above, loose matches on Subject: below --
2007-06-27 21:36 7091
2007-07-08 8:01 ` Janos Haar
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.468B005A.0000127A@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 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.