From: Tejun Heo <htejun@gmail.com>
To: Jonathan Bell <doggs.lay.eggs@googlemail.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Errors when copying between drives on a SiI3114 controller under kernel 2.6.18
Date: Sun, 08 Oct 2006 13:33:42 +0900 [thread overview]
Message-ID: <45287FA6.5020906@gmail.com> (raw)
In-Reply-To: <op.tg1yx12kxci36i@akima>
Hello.
Jonathan Bell wrote:
> The problem is that when copying a file off one drive on the controller to
> another on the same controller, be it via dd or cp, the file that gets
> written becomes corrupted along with the filesystem itself. Here is an
> extract from dmesg:
That's very weird.
> [12689.451466] attempt to access beyond end of device
> [12689.451475] sdb1: rw=0, want=2339438600, limit=488392002
> [12689.451480] attempt to access beyond end of device
> [12689.451484] sdb1: rw=0, want=18446744056529747976, limit=488392002
> [12689.453822] attempt to access beyond end of device
> [12689.453831] sdb1: rw=0, want=2339438600, limit=488392002
> [12689.453834] Buffer I/O error on device sdb1, logical block 292429824
> [12689.453935] attempt to access beyond end of device
> [12689.453938] sdb1: rw=0, want=2339438600, limit=488392002
> [12689.453941] Buffer I/O error on device sdb1, logical block 292429824
[--snip--]
> I would like some help tracking down the cause of this problem as I have
> practically exhausted the methods currently at my disposal - my best guess
> at the moment is that data being written to another port is being trampled
> on somehow but only when there is I/O active on another port. I will
> continue testing to see if simultaneous writes to multiple drives on a
> controller causes the same problem.
Can you repeat the test using raw devices - /dev/sdX? I don't think
filesystem is at fault, so let's rule it out. Also, please post the
result of lspci -nvvvxxx
Thanks.
--
tejun
next prev parent reply other threads:[~2006-10-08 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 13:11 Errors when copying between drives on a SiI3114 controller under kernel 2.6.18 Jonathan Bell
2006-10-08 4:33 ` Tejun Heo [this message]
2006-10-08 13:19 ` Jonathan Bell
2006-10-09 8:38 ` Tejun Heo
2006-10-09 8:43 ` Tejun Heo
2006-10-09 14:49 ` Jonathan Bell
2006-10-11 22:35 ` Jonathan Bell
2006-10-14 12:13 ` Tejun Heo
2006-10-22 15:33 ` Jonathan Bell
2006-10-23 2:22 ` Tejun Heo
2006-10-23 10:13 ` Alan Cox
2006-10-23 13:35 ` Jonathan Bell
2006-10-23 14:09 ` Alan Cox
2006-10-30 20:53 ` Jonathan Bell
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=45287FA6.5020906@gmail.com \
--to=htejun@gmail.com \
--cc=doggs.lay.eggs@googlemail.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.