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 - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
