| Summary: | Burning and verifying files adding up to more then 20GB errors/crashes at 99% burn completion Code 253 (no verify) | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Vance Lohoff <vancel> |
| Component: | Data Project | Assignee: | k3b developers <k3b> |
| Status: | REPORTED --- | ||
| Severity: | critical | CC: | dpmclaren, gordoneki, michalm, trueg |
| Priority: | NOR | ||
| Version: | 2.0.80 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| URL: | https://forums.opensuse.org/showthread.php/508201-K3b-will-not-complete-a-burn-and-verify-cycle-on-BD-R-media | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | k3b slow burn of BLU-RAY and closing error if <25GB | ||
|
Description
Vance Lohoff
2015-07-05 23:04:49 UTC
Created attachment 95639 [details]
k3b slow burn of BLU-RAY and closing error if <25GB
Using K3b to burn dar archive slices. If the slice file is 25GB, k3b burns BLU-RAY disks at full speed, about 6X on an LG BD-RE WH14NS40, and the device buffer shows 100%. However,if the file is < 25G, e.g. the final slice in the backup, k3b burns at about 2.5X, the device buffer shows 99% (never 100%), and the burn exits with an error (see screen shot). However, the disk is burned correctly despite the message, that is, the disk mounts OK, and dar -t passes it as correct. I am running on UBUNTU 4.04. I hope this info is helpful in addressing the BLU-RAY burn problems already reported.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Very likely this happens because the Blu-ray ran out of space. While calculating the remaining space on the Blu-ray, K3b does not consider file system overhead. To avoid this problem, leave a margin of remaining space of about 1%. In my experience, mkisofs crashes if the disc runs out of space before all files were written. Otherwise, it finishes without error. Some optical drives support overburning, which might be able to squeeze out a few hundred megabytes at the end. It appears your disc ran out of its actual capacity. According to my experience, K3b or the optical drive overestimates the Blu-ray capacity by around 280 MB. What's worse: Because the session is unclosed, Windows can not read any files from it. Only Linux can. This is not the fault of K3b, but Microsoft. The only way to read files from an unclosed session on Windows is by using third-party tools like IsoBuster. It has its own file browser. Windows recognizes unclosed sessions on packet writing discs, but not on unclosed sequentially burned discs. When adding files, I recommend keeping a headroom of 280 MB at the end. Even with overburning activated, the disc drive might refuse to go beyond a certain point, and K3b can not overrule the disc drive. Try running dvd+rw-mediainfo on that disc (in case you read this). If the recording mode is SRM+POW, it reserved 256 MB as spare area to be able to simulate overwriting to replace damaged data. This is not necessary on blank media. On growisofs (command-line tool), this can be disabled using -use-the-force-luke=spare:none . |