mkisofs: Value too large for defined data type. File /mnt/backups/toburn/home.002 is too large - ignoring
Note that last two lines are output from mkisofs, an external program [relative to growisofs]. They have nothing to do with overburn protection. It's just that mkisofs refuses to handle files larger that 2GB-2 bytes. One can argue if it's a bug or feature, but there is more or less solid ground for such behaviour. Well, at least in Linux context. It takes two to dance tango, right? If mkisofs puts file larger than 2GB-2 bytes to resulting ISO9660 image, Linux kernel won't let you access data beyond first 16MB anyway. Yes, it's possible to patch the kernel in which case you'll be able to access files of arbitrary size, files residing on ISO9660 volume. But it again will be only 1/2 of solution [needed in this particular case]. In order to break the 4GB-1 byte barrier, you'll have to modify mkisofs to support multi-extent files.
Bottom line. Forget about putting files larger than 2GB-2 bytes to ISO9660 volumes for now.
How to proceed? If you *ougth to* put home.002 to an ISO9660 volume, split it to three(!) files. Alternative is to burn it as image with 'growisofs -Z /dev/cdrom=home.002' and access the data with the program you've created the archive with. E.g. if it's a tar archive, 'tar tf /dev/cdrom'.
My bad. I'll just generate the files in smaller chunks. It's good to know why the errors popped up, though. Thanks for the help!
Chad Martin
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
