Bug 62431
Summary: | CD reading appears to read-ahead beyond end of track causing "Input/output error" | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Dale Worley (worley) |
Component: | Other | Assignee: | io_other |
Status: | RESOLVED WILL_NOT_FIX | ||
Severity: | normal | CC: | alan |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 3.11.2-201.fc19.x86_64 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Dale Worley
2013-10-02 18:21:14 UTC
The messages that appear in /var/log/messages are: Sep 27 17:26:27 hobgoblin kernel: [166448.858612] sr 1:0:0:0: [sr0] Unhandled sense code Sep 27 17:26:27 hobgoblin kernel: [166448.858619] sr 1:0:0:0: [sr0] Sep 27 17:26:27 hobgoblin kernel: [166448.858621] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 27 17:26:27 hobgoblin kernel: [166448.858624] sr 1:0:0:0: [sr0] Sep 27 17:26:27 hobgoblin kernel: [166448.858627] Sense Key : Hardware Error [current] Sep 27 17:26:27 hobgoblin kernel: [166448.858631] sr 1:0:0:0: [sr0] Sep 27 17:26:27 hobgoblin kernel: [166448.858635] Add. Sense: Timeout on logical unit Sep 27 17:26:27 hobgoblin kernel: [166448.858639] sr 1:0:0:0: [sr0] CDB: Sep 27 17:26:27 hobgoblin kernel: [166448.858641] Read(10): 28 00 00 04 ce ba 00 00 34 00 Sep 27 17:26:27 hobgoblin kernel: [166448.858651] end_request: I/O error, dev sr0, sector 1260264 Sep 27 17:26:27 hobgoblin kernel: [166448.858656] Buffer I/O error on device sr0, logical block 157533 Sep 27 17:26:27 hobgoblin kernel: [166448.858665] Buffer I/O error on device sr0, logical block 157534 Sep 27 17:26:27 hobgoblin kernel: [166448.858668] Buffer I/O error on device sr0, logical block 157535 Sep 27 17:26:27 hobgoblin kernel: [166448.858671] Buffer I/O error on device sr0, logical block 157536 Sep 27 17:26:27 hobgoblin kernel: [166448.858675] Buffer I/O error on device sr0, logical block 157537 Sep 27 17:26:27 hobgoblin kernel: [166448.858678] Buffer I/O error on device sr0, logical block 157538 Sep 27 17:26:27 hobgoblin kernel: [166448.858681] Buffer I/O error on device sr0, logical block 157539 Sep 27 17:26:27 hobgoblin kernel: [166448.858684] Buffer I/O error on device sr0, logical block 157540 Sep 27 17:26:27 hobgoblin kernel: [166448.858687] Buffer I/O error on device sr0, logical block 157541 Sep 27 17:26:34 hobgoblin kernel: [166455.617288] sr 1:0:0:0: [sr0] Unhandled sense code Sep 27 17:26:34 hobgoblin kernel: [166455.617294] sr 1:0:0:0: [sr0] Sep 27 17:26:34 hobgoblin kernel: [166455.617297] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 27 17:26:34 hobgoblin kernel: [166455.617300] sr 1:0:0:0: [sr0] Sep 27 17:26:34 hobgoblin kernel: [166455.617302] Sense Key : Hardware Error [current] Sep 27 17:26:34 hobgoblin kernel: [166455.617307] sr 1:0:0:0: [sr0] Sep 27 17:26:34 hobgoblin kernel: [166455.617311] Add. Sense: Timeout on logical unit Sep 27 17:26:34 hobgoblin kernel: [166455.617314] sr 1:0:0:0: [sr0] CDB: Sep 27 17:26:34 hobgoblin kernel: [166455.617316] Read(10): 28 00 00 04 ce ec 00 00 02 00 Sep 27 17:26:34 hobgoblin kernel: [166455.617326] end_request: I/O error, dev sr0, sector 1260464 Sep 27 17:26:34 hobgoblin kernel: [166455.617330] quiet_error: 17 callbacks suppressed Sep 27 17:26:34 hobgoblin kernel: [166455.617333] Buffer I/O error on device sr0, logical block 157558 The end of a CD-R is not actually precisely defined, which is what causes this. There is a good argument it should be quiet about it, and we do try to be on devices that return the error codes we expect. (In reply to Alan from comment #2) > The end of a CD-R is not actually precisely defined, which is what causes > this. It sounds as if there is no proper EOF mark on the data. So applications that do not attempt to read beyond the data that is actually written (e.g., when it contains an ISO file system) will succeed, but applications that "read until EOF" will get an I/O error, because the driver can't tell if it has reached EOF or if it has hit a bad part of the media. Since this problem seems to be unfixable (due to the organization of CD-ROM data), I am marking it as RESOLVED/WILL_NOT_FIX. |