Bug 255483 - K3b computes available size incorrectly for Blu-ray due to defect management
Summary: K3b computes available size incorrectly for Blu-ray due to defect management
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Data Project (show other bugs)
Version: 2.0.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-28 11:25 UTC by Alexander
Modified: 2023-02-11 03:51 UTC (History)
1 user (show)

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


Attachments
write log (5.10 KB, text/plain)
2010-10-28 11:27 UTC, Alexander
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander 2010-10-28 11:25:25 UTC
Version:           2.0.1 (using KDE 4.5.2) 
OS:                Linux

There is a bug when computing available size on a Blu-ray (BD-R) disk in both growisofs and k3b.

Basically, when defect management is on (which is default for growisofs), k3b doesn't take into account the fact that growisofs reserves 250MB for spare sectors and will happily accept more data than BD-R can handle, leading to write errors near the end. Due to another bug in growisofs, growisofs also accepts that data.

I'm attaching a write log.

Some more details here:
http://lists.debian.org/cdwrite/2010/10/msg00046.html

Reproducible: Didn't try

Steps to Reproduce:
Write an unformatted BD-R so that k3b shows only about 100MB free space left.

Actual Results:  
Write error near the end.

Expected Results:  
K3b should prevent the user from writing so much data. It should take into account the reserved 250MB area, or allow the user to control that.

openSUSE 11.3 x86_64.
Pioneer BDR-205 blu-ray writer (firmware 1.09).
TDK 4x BD-R media.
Comment 1 Alexander 2010-10-28 11:27:13 UTC
Created attachment 52935 [details]
write log
Comment 2 Andrew Crouthamel 2018-11-12 02:45:14 UTC
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!
Comment 3 Andrew Crouthamel 2018-11-21 04:39:13 UTC
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!
Comment 4 Justin Zobel 2023-01-12 01:57:52 UTC
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!
Comment 5 Alexander 2023-01-12 09:07:17 UTC
I do not use K3b or Blu-rays anymore, so I cannot verify whether the bug is still present. Sorry.
Comment 6 Bug Janitor Service 2023-01-27 05:07:00 UTC
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!
Comment 7 Bug Janitor Service 2023-02-11 03:51:54 UTC
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!