Created attachment 48124 [details] K3b debug log of Input/output error at end of BD-R burn Version: 1.92.0 (using KDE 4.4.4) OS: Linux When burning a BD-R when 99% finished writing, I get "Fatal Error during record: Input/output error" in the Burn Progress dialog. The debug log is attached (edited for brevity - it shows no errors and nothing interesting). All 56K resulting files of a 21.6GB Data Project EXCEPT the first are corrupt. A corrupt file is corrupt in a regular way. The original and copy are the same size, but the copy has omitted some segments of the original file, and has a few garbage segments. The garbage segments are not at the same offsets as the omitted segments. See below a sample corrupt file I took apart, 6.8MB in length. offsets in octal offset contents 0: 1000000-1 random mostly non-zero garbage 1000000:14640000-1 original file 0:13640000-1 (original file 13640000:14640000-1 omitted) 14640000:16240000-1 original file 14640000:16240000-1 16240000:17440000-1 garbage (copied original file 15040000:16240000-1) 17440000:33262500 original file 16240000:32062500 (original file 32062500+1:33262500 omitted) So two chunks of the original file were omitted, length 256KB and 256KB+64KB, and two pieces of buffer garbage of equal length were picked up, though they weren't inserted at the offsets of the omitted chunks. This is a systematic programmatic error: the sizes and offsets of the corruption are sufficiently "round" so as to be recognizably non-random. The layout is as if the original file were split into two contiguous partitions, and the contents of each partition "slid" to higher addresses, knocking off the end, and leaving garbage trailing behind it. I have tried two brands of BD-R media, Memorex, and Verbatim, and the corrupt files have exactly the same content on each brand of disk, so I don't think it's a media compatibility problem. As a side note, I can write the same contents successfully to a BD-RE disk, so the error must be in a path unique to BD-R. I also tried to write a single very small file to BD-R, and failed with the same I/O error @99% (though the file was not corrupt). So I don't think the problem is size related. I also tried to write to BD-R with multi-session, and failed the same way. If the multi-session disk is burned in another session, mkisofs crashes (subject for another bug report). Reproducible: Always Steps to Reproduce: Insert BD-R unused media. Select Data Project. Browse and add files to project (21.6GB worth) Select Burn from Project Menu. Click Burn in Data Project dialog. wait until error appears in Burn Progress dialog Actual Results: burn fails with "X Fatal error during record: Input/output error" Expected Results: successful burn, and data validation succeeds Everything is as direct as it can be - the only non-default K3b option selected was "Verify written data".
Here is the code which produces this message: > emit infoMessage( i18n( "Fatal error during recording: %1", QString::fromLocal8Bit( ::strerror(exitCode) ) ), K3b::Job::MessageError ); Growisofs returned non-zero exit code and "input/output" is a message corresponding to the code. In short, this is upstream issue.
I confirm the upstream issue - command line burn from growisofs fails in the same way, with an informative message: > growisofs -Z /dev/sr1="/home/sbalfour/Downloads/russian.iso" -dvd-compat -speed=4 ... /dev/sr1: closing session :-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]: Input/output error It'd be really, REALLY nice if we could capture that message in the K3b debug log! This bug should be moved to the dvd+rw-tools package in the Ubuntu database at https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools. It's also two major bugs: one for the session close failure, and another for the file corruption (apparently unrelated). Not capturing the stderr output from upstream programs in k3b debug log can probably be split off as a <minor> bug report against k3b, and remain here.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!