Menu
▾
▴
Re: [Cdw-devel] Bugs prior to 0.5 release
|
From: <cdw...@li...> - 2010-07-14 23:12:49
|
14) Time Time Until Completion dialog doesn't seem correct with growisofs.
although I see within stderr:
cdw_growisofs_pr_handle_writing_data():669: INFO: submatch 15, minutes
remaining: "34" -> 34
cdw_growisofs_pr_handle_writing_data():676: INFO: submatch 16, seconds
remaining: "02" -> 2
cdw_growisofs_pr_handle_writing_data():711: INFO: progress_string = "0.1/2.6
MB"
cdw_growisofs_pr_handle_writing_data():716: INFO: done / total = 0.051933 /
2.596674 (task: burn from files)
cdw_growisofs_pr_handle_writing_data():742: INFO: ETA: minutes = 34, seconds =
2 -> string = "ETA: 34:02"
cdw_growisofs_pr_handle_writing_data():655: INFO: submatch 6, decimal part of
percentage: "3" -> 3
cdw_growisofs_pr_handle_writing_data():662: INFO: submatch 7, fractional part
of percentage: "0" -> 0
cdw_growisofs_pr_handle_writing_data():669: INFO: submatch 15, minutes
remaining: "24" -> 24
cdw_growisofs_pr_handle_writing_data():676: INFO: submatch 16, seconds
remaining: "06" -> 6
cdw_growisofs_pr_handle_writing_data():711: INFO: progress_string = "0.1/2.6
MB"
cdw_growisofs_pr_handle_writing_data():716: INFO: done / total = 0.077900 /
2.596674 (task: burn from files)
cdw_growisofs_pr_handle_writing_data():742: INFO: ETA: minutes = 24, seconds =
6 -> string = "ETA: 24:06"
I know a 3.2M file doesn't take this long to write. And then I see ETA jump down
from 34 minutes to approximately 5 minutes (guessing) during the writing.
It seems cdw_growisofs_pr_handle_writing_data is reporting inflated times.
When I execute growisofs via command line, I get none of these inflated values
with a very small /tmp/tmp.iso (2M). Growisofs via command line shows:
growisofs -dvd-compat -Z /dev/dvdrw=/tmp/tmp.iso
And the write session was completed within a few minutes -- but growisofs didn't
show any ETA times, only an initial ???.
After trying to run the same growisofs command but with time, I get the long
delay now.
Matter of fact, I'm seeing likely a kernel bug here:
Jul 14 14:49:29 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Jul 14 14:49:29 [kernel] end_request: I/O error, dev sr0, sector 0
Jul 14 14:49:29 [kernel] Buffer I/O error on device sr0, logical block 0
Jul 14 14:49:38 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
Jul 14 14:49:38 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 14:49:38 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
Jul 14 14:49:38 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
Jul 14 14:49:38 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 0e 00 00 02 00
Jul 14 14:49:38 [kernel] end_request: I/O error, dev sr0, sector 56
Jul 14 14:49:38 [kernel] Buffer I/O error on device sr0, logical block 7
Jul 14 14:49:47 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
Jul 14 14:49:47 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 14:49:47 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
Jul 14 14:49:47 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
Jul 14 14:49:47 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Jul 14 14:49:47 [kernel] end_request: I/O error, dev sr0, sector 0
Jul 14 14:49:47 [kernel] Buffer I/O error on device sr0, logical block 0
Jul 14 14:49:56 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
Jul 14 14:49:56 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 14:49:56 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
Jul 14 14:49:56 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
Jul 14 14:49:56 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Jul 14 14:49:56 [kernel] end_request: I/O error, dev sr0, sector 0
Jul 14 14:49:56 [kernel] Buffer I/O error on device sr0, logical block 0
This seems to be causing the long delay at times when writing -- this could be
either the media becoming unwritable (RW media) or other error -- or growisofs
could be doing a automatic erase??
Executing 'builtin_dd if=/tmp/tmp.iso of=/dev/dvdrw obs=32k seek=0'
/dev/dvdrw: "Current Write Speed" is 2.5x1352KBps.
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
0/3330048 ( 0.0%) @0x, remaining ??:?? RBU 10.0% UBU 0.0%
32768/3330048 ( 1.0%) @0.0x, remaining 40:15 RBU 9.9% UBU 100.0%
32768/3330048 ( 1.0%) @0.0x, remaining 45:16 RBU 9.9% UBU 100.0%
32768/3330048 ( 1.0%) @0.0x, remaining 50:18 RBU 9.9% UBU 100.0%
65536/3330048 ( 2.0%) @0.0x, remaining 28:13 RBU 9.8% UBU 100.0%
...snip...
Oh Wow. This is turning out to be an extremely long write session this time!
This is starting to appear more like a growisofs issue or even bug. Or even
undocumented kernel bug? <shrugs>
syslog is dumping this:
14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Jul 14 15:04:30 [kernel] end_request: I/O error, dev sr0, sector 0
Jul 14 15:04:30 [kernel] Buffer I/O error on device sr0, logical block 0
Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Jul 14 15:04:40 [kernel] end_request: I/O error, dev sr0, sector 0
Jul 14 15:04:40 [kernel] Buffer I/O error on device sr0, logical block 0
Seems like redundant duplicate errors, including the last error.
At this point, I just usually toss the RW media -- seems it only lasts sometimes a few writes. :-/
Or am I dumb and not realizing something???
--
Roger
http://rogerx.freeshell.org/
|
