Bug 461191 - BD-R LOGICAL BLOCK ADDRESS OUT OF RANGE: No space left on device
Summary: BD-R LOGICAL BLOCK ADDRESS OUT OF RANGE: No space left on device
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 22.04.2
Platform: Debian testing Linux
: NOR grave
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-30 09:55 UTC by Gery
Modified: 2024-03-19 17:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
data does not fit on disk (1.10 MB, text/plain)
2022-10-30 09:55 UTC, Gery
Details
K3b advanced settings (52.09 KB, image/png)
2024-03-19 17:35 UTC, Gordon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gery 2022-10-30 09:55:33 UTC
Created attachment 153315 [details]
data does not fit on disk

SUMMARY
wasted already 3 BD-R with error " data does not fit on disk ". 
In fact 23.1GiB BD-R project still had 242.1MiB space available .

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: pre-formatting blank BD-R for 24.8GB...
/dev/sr0: "Current Write Speed" is 12.3x4390KBps.

24725422080/24771979264 (99.8%) @3.5x, remaining 0:03 RBU 100.0% UBU  98.3%
:-[ WRITE@LBA=b87400h failed with SK=5h/LOGICAL BLOCK ADDRESS OUT OF RANGE]: No space left on device
:-( write failed: No space left on device
/dev/sr0: flushing cache
/dev/sr0: closing track

STEPS TO REPRODUCE
1.  Burn BD-R disk nearly full . 
2. 
3. 

OBSERVED RESULT
 error " data does not fit on disk ". 

EXPECTED RESULT
write succeed . 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Debian Bookworm  ,
System
-----------------------
K3b Version: 22.4.2
KDE Version: 5.94.0
Qt Version:  5.15.4
Kernel:      5.15.0-2-amd64

Used versions
-----------------------
mkisofs: 1.1.11
growisofs: 7.1

ADDITIONAL INFORMATION
Comment 1 Gordon 2024-03-19 17:32:56 UTC
Does it happen if you leave 300 MB free at the end?

Try enabling "Allow overburning" in the advanced settings. (screenshot: https://imgur.com/a/MFHaAUQ )

It appears K3b does not calculate file system overhead when calculating the space.
Comment 2 Gordon 2024-03-19 17:35:37 UTC
Created attachment 167478 [details]
K3b advanced settings

I didn't realize I can add attachments to comments too.
Here is a copy of the screenshot from the preceding comment I posted to Imgur, in case Imgur fails to keep it.