Bug 246170 - [PATCH] default BDR (SRM+POW) data project allows 256MB excess data to be "burned"
Summary: [PATCH] default BDR (SRM+POW) data project allows 256MB excess data to be "bu...
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Data Project (show other bugs)
Version: 1.92.0
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-07-29 16:46 UTC by Stuart Balfour
Modified: 2018-10-27 04:02 UTC (History)
2 users (show)

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


Attachments
fix post - 2.6.18 linux header reshuffle leaves MAXINT undefined (292 bytes, patch)
2010-07-29 16:46 UTC, Stuart Balfour
Details
enable -dao mode for BDR (2.27 KB, patch)
2010-07-29 16:51 UTC, Stuart Balfour
Details
avoid growisofs error due to invalid attempt to close session for SRM+POW mode (2.18 KB, patch)
2010-07-29 16:56 UTC, Stuart Balfour
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Balfour 2010-07-29 16:46:54 UTC
Created attachment 49643 [details]
fix post - 2.6.18 linux header reshuffle leaves MAXINT undefined

Version:           1.92.0 (using KDE 4.4.5) 
OS:                Linux

The default burn format for BDR is SRM+POW, which reserves 256MB of spare
clusters for defect management and pseudo-overwrite capacity.  The green scroll
bar shows *unformatted* capacity of 23.3GB and allows user to add that much data
to the project, when in fact only 23.3GB - 0.256GB = 23.05GB of data can actually
be burned.  SCSI READ_CAPACITY on a SRM+POW formatted BDR returns 24756879360,
which is 23.057GB.  Burning the disk results in mkisofs (really genisoimage)
crash 99.1% into the burn.  The names of the last several files totaling 256MB
will appear on the disk with their correct sizes, but their content will be
missing.  

Reproducible: Didn't try

Steps to Reproduce:
Insert unformatted BDR into the drive.
Select Data Project.
Add file(s) to the project total larger than 23.057GB (but less than 23.3GB)
Select Burn from Project menu.  (Use all default settings.)
Click Burn
  

Actual Results:  
Progress windows shows "mkisofs crashed" 99.1% into burn.  
Last [up to] 256MB of files are missing or corrupt.


Expected Results:  
All data burned correctly.

OS: Linux (i686) release 2.6.32-23-generic
Compiler: cc
K3b version is 1.92.0 RC3-2 with 3 unreleased patches to growisofs component
of dvd+rw-tools 7.1 to fix BDR burn problems.  Without the patches,the BDR burn
will fail in growisofs sooner, with a different error.  However, the UI problem
can be understood and reproduced without atually needing to burn.  The
problem would not have been able to be noticed and reported until I was able
to get a disk to burn to the end.  Developers attempting to reproduce this
problem exactly (see the mkisofs crash) will need at least the three patches to
growisofs I've attached.
Comment 1 Stuart Balfour 2010-07-29 16:51:12 UTC
Created attachment 49644 [details]
enable -dao mode for BDR

2nd of three patches to dvd+rw-tools 7.1 reproduce k3b problem
Comment 2 Stuart Balfour 2010-07-29 16:56:25 UTC
Created attachment 49645 [details]
avoid growisofs error due to invalid attempt to close session for SRM+POW mode

third of three patches to dvd+rw-toos 7.1 to reproduce bug in k3b
Comment 3 Albert Astals Cid 2014-09-28 00:44:36 UTC
I'm confused, this patches don't apply to K3b, do they?
Comment 4 Andrew Crouthamel 2018-09-25 03:56:34 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 set the bug status 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 5 Andrew Crouthamel 2018-10-27 04:02:19 UTC
Dear Bug Submitter,

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!