Jiri Slaby wrote:
Hello,
I get this with 2.6.17-rc5-mm3 kernel:
..
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 245920 512-byte hdwr sectors (126 MB)
..
now read and write and sync or umount, then:
---
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1575
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1583
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1591
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1599
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1607
sd 10:0:0:0: SCSI error: return code = 0x10070000
end_request: I/O error, dev sdb, sector 1615
... and so on. data are maybe there, but it takes so long to write a meg file.
sometimes
..
This *looks* like maybe the drive reported a sector read error,
and the standard "fail the whole request one block at a time"
error mechanism from sd.c has kicked in.
I have a patch to fix this behaviour (in sd.c), but it has not yet
been decided whether to go upstream with it or not.
The same behaviour bites anything from libata as well,
and possibly also (not verified) firewire drives.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
