Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Something I have uncovered while searching for the answer to this problem.
1. This seems to be a 32 bit issue. The maximum file size is 2GB on 32 bit systems.
2. many 2.4 series kernels cannot "fool" the physics of the architecture, so the limit is still 2GB.
3. the 2.6 kernel is supposed to have fixed this issue (which means a nasty hack like ide-scsi?)
4. Even if your kernel can fool itself into generating files larger than 2GB, many applications aren't coded to take advantage of this feature.
Therefore, if you can create the tarball bigger than 2GB your kernel is obviously modern enough, butyour tools aren't equipped to handle this. Check for newer versions supporting files larger than 2GB.
Originally posted by vectordrake
1. This seems to be a 32 bit issue. The maximum file size is 2GB on 32 bit systems.
As far as I know, this limitation has been lifted on many, if not all, modern 32-bit systems. I've been using kernel 2.6 since 2.6.0, and I haven't had any problem creating a file larger than 2 GB. I've never had to use the SCSI emulation (the "ide-scsi" thing) with kernel 2.6 at all, either.
The cdrtool (i.e. mkisofs, cdrecord and others) supports files larger than 2GB starting with version 2.01, although creating an ISO image of larger than 2GB has never been a problem for me, even though I was using mkisofs 2.0.
I just upgraded cdrtool to 2.01. mkisofs can now create an image from an original file larger than 2GB.
I'd like to hang with the guy. he seems to have his head screwed on. He's one of the most famous people in IT and he still tries to put his family first
I'd have to agree with a lot of what's criticized in the kernel, since I'm running one that uses most of the "foreward-thinking" patches.
Simply upgrade your distro.
To burn dvd sized image or file you need growisofs part of cdrtool.
K3b is able to burn 7,5 GB DuobleLayer DVD simply because it use it!
Needed at least version 5.21 to burn double layer dvd.
Originally posted by walker Simply upgrade your distro.
To burn dvd sized image or file you need growisofs part of cdrtool.
K3b is able to burn 7,5 GB DuobleLayer DVD simply because it use it!
Needed at least version 5.21 to burn double layer dvd.
The package I got for my distro says 2.01a38. I assume it means 2.01 alpha-38.
dvd+rw-tools contain growisofs, which I use to burn an ISO image to a DVD media.
One thing I would do is run "md5sum" on the original tarball and the one created by mkisofs to compare the checksums. If they are different, then I must agree that your mkisofs tool is somehow not working correctly.
Hi Daihard,
I went to look at the aplha version that you have, but they seem to have moved it out from the ftp.
Is there any way that you can mail me the alpha version you have.
The md5sum trick worked, both checksums are different, they just proved that mkisofs isnt able to make iso from file size > 2GB.
the version I have is pure 2.01. its not an alpha, maybe they solved the problem in that alpha release.
Originally posted by vectordrake Perhaps since there's a md5sum error, be sure to send him the md5sum of your tarball too.you likely thought about that, but, you know....
Distribution: Redhat Linux 8 & 9, Fedora Core 2, XP
Posts: 301
Rep:
I'm using K3B 0.11 and dvd+rw-tools 5.21.4.10.8 but I cannot burn my 2.2GB tar backup file into DVD...
You guys reckon reiserfs would fix this?
I am having trouble starting a RAID1 FC2 with reiserfs though
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.