Bug 85705

Summary:	k3b does not warn when burning files >2GB
Product:	[Applications] k3b	Reporter:	Justin M. Forbes <64bit_fedora>
Component:	general	Assignee:	Sebastian Trueg <trueg>
Status:	RESOLVED FIXED
Severity:	normal	CC:	z9atqts02
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Justin M. Forbes 2004-07-22 18:07:34 UTC

Version:            (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
OS:                Linux

Pushing this upstream from Redhat Bugzilla #128374

Description of problem:
Note: this may be a problem in dvd+rw-tools/mkisofs, really.

When burning a file larger than 2GB to a DVD+RW (this is that I tried,
I am quite confident it happens with all other types of DVD media,
too), burning the file works just fine, and the resulting media can be
mounted without problems.

However, accessing portions of the file beyond the 2GB barrier fails
(IMHO iso9660 has a 2GB file size limit).

When enabling UDF the media is mounted as UDF, and the complete file
can be accessed.

So, k3b ought to warn the user that there may be trouble reading the
files he is about to burn unless he enables UDF.

Version-Release number of selected component (if applicable):
k3b-0.11.12-2

How reproducible:
Always

Steps to Reproduce:
1. Burn a file larger than 2GB to a DVD
2. Try to read back the file from the media

Comment 1 Steve Bonds 2004-07-26 22:44:18 UTC

This is a problem with mkisofs, however given that this problem exists it would be helpful if k3b could work around it, or at least warn the user when it could be a problem.

Newer versions of mkisofs (tested with cdrtools 2.01 alpha 34) will include files over 2GB, but the Linux iso9660 filesystem driver won't interpret this correctly and the result is a file of length [original modulus 2GB] and a corrupted file.

This post from the cdrecord mailing list describes the problem, provides a solution, then describes why you don't want to use the solution:

http://lists.debian.org/cdwrite/2003/12/msg00101.html

My suggestion on a fix would be a warning dialog (that could be disabled) that pops up after adding files that lists the files larger than 2GB that may be skipped.  (Similar to the dialog if one or more files can't be read.)

Comment 2 Sebastian Trueg 2004-08-03 13:39:35 UTC

*** Bug has been marked as fixed ***.

Comment 3 Oliver Jones 2005-01-24 14:54:27 UTC

A more intelligent approach would be to automatically enable UDF (perhaps with an info dialog telling the user that this is happening, but this is probably not necessary, a status bar message perhaps) when a file larger than 2GB is added to the DVD.  Turning off UDF support with a file larger than 2GB in the file list should also issue a warning.

I just wrote a couple of coasters today because I forgot that ISO9660 has a limit of 2GB.  K3B 0.11.14 doesn't warn you when you try and add files larger than 2GB to a DVD.  When it comes time to burn it seems as thouse mkisofs/growisofs just ignores the file and continues.  I couldn't figure out why my burns were empty and only taking a couple minutes when they should have been taking 30 or more.  I was trying to burn a single 4GB tar file to DVD.

Most frustrating.  I didn't think of using UDF as I don't know much about it.  Instead I just used split to turn the tar into four 1GB files which I can rejoin later.  Now my burn has worked just fine without using UDF.