! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Xfburn doesn't burn large files in Data Compilation
Status:
RESOLVED: FIXED

Comments

Description Nikos Balkanas 2014-03-29 20:47:46 CET
I am using xfburn for my home PC's backups. These are usually large .tgz archives. When trying to back them to a DVD with xfburn I get:

"<file> cannot be added to the composition, because it exceeds the maximum allowed file size for iso9660"

I don't know what this is for, I have seen much larger .iso images, and using CDBurner for windows, I never had this problem.

In fact, if adding also smaller files, it will proceed and burn the smaller files, while leaving the larger ones out. That is wrong. It should refuse the whole compilation until user manually removes the larger files.
Comment 1 David Mohr 2014-03-30 19:56:45 CEST
Thanks for the report. This has been fixed in git rev. ba1fa942ff1014120759863ac1fa88860f8149c1 , now large files will be allowed.

But already before the larger files didn't end up in the compilation. What's the point of adding them when they can't be burned?
Comment 2 Nikos Balkanas 2014-03-30 20:21:04 CEST
I add a whole folder in the compilation, having both large and small files in subfolders. Then the warning comes up. Yet the folder in the compilation still looks fine. You peek inside, level 1 looks OK, 2nd too, nothing missing. You decide you misunderstood the warning (there couldn't be a size restriction - no other burning software has one) and since you are in a hurry and don't want to go through all the subfolders, you go ahead and burn it.

You have just waisted a good DVD. Correct response would be to transfer the larger files in the compilation window, and not allow the compilation to proceed until user has removed them himself.

Since it is a user action that puts them in, a user action should also take them out, so that user is in full knowledge of which files are involved. Warning didn't even say which were the offensive files or not, or even which is the size threshold.
Comment 3 David Mohr 2014-03-30 20:30:32 CEST
You're right about the manual removal. Patches are welcome.

The error message has always included the filename that was too big.

But, like you said yourself, this won't be happening very often anymore now that the size limit has increased to what iso9660 can actually support.

Please try the git version or email me for a link to a tarball.

Bug #10779

Reported by:
Nikos Balkanas
Reported on: 2014-03-29
Last modified on: 2014-03-30

People

Assignee:
Xfburn Bug Triage
CC List:
2 users

Version

Attachments

Additional information