Hi, on what kind of fs do you create this image ?

On Thu, 2005-02-24 at 14:12 +0100, A. Lanza wrote: > Hi list, > > i'm trying to burn a DVD using k3b, as i usually do for CD burning. I'm > using 4,7GB size DVD-R. The problem is that i cannot burn a 4,4GB. file. > The file is exactly 4,613,704,668 bytes long. > > The message i get from k3b is the following: > /usr/bin/mkisofs: Value too large for defined data type > and then > File <file> is too large - ignoring > > It seems like the problem is the file size, but that file should fit in > a DVD, shouldn't it? Is there any limit in the size of files written to > DVD? > > Thanks, > > Alf > > -- ======================================================= Alexander Spanke System Analyst NEC High Performance Computing Europe GmbH Prinzenallee 11 D-40549 Duesseldorf, Germany Tel: +49 211 5369 146 aspanke(a)hpce.nec.com Fax: +49 211 5369 199 http://www.hpce.nec.com =======================================================

On Thu, 2005-02-24 at 14:12 +0100, A. Lanza wrote: > Hi list, > > i'm trying to burn a DVD using k3b, as i usually do for CD burning. I'm > using 4,7GB size DVD-R. The problem is that i cannot burn a 4,4GB. file. > The file is exactly 4,613,704,668 bytes long. > > The message i get from k3b is the following: > /usr/bin/mkisofs: Value too large for defined data type > and then > File <file> is too large - ignoring > > It seems like the problem is the file size, but that file should fit in > a DVD, shouldn't it? Is there any limit in the size of files written to > DVD? > > Thanks, > > Alf > I create a data DVD by using { file -> new project -> new data DVD project } then creating the file list to be included with drag-n-drop. >

It seems to me that the question is not whether the file fits into the DVD, but rather if its size fits into the variables used by mkisofs to address files and/or doing space calculations. ("mkisofs" is the command used to actually burn the DVD; k3b is just a front-end to other commands.)

Felipe Alfaro Solana wrote: > On 25 Feb 2005, at 11:19, Toralf Lund wrote: > >> It seems to me that the question is not whether the file fits into >> the DVD, but rather if its size fits into the variables used by >> mkisofs to address files and/or doing space calculations. ("mkisofs" >> is the command used to actually burn the DVD; k3b is just a >> front-end to other commands.) > > > > No. mkisofs is the program used to create the image, while cdrecord > or growisofs is the one used to burn that image. Urgh. Minor slip, there."The program used to create the filesystem", I meant to say... But my point remains: The problem appears to be internal mkisofs limitations, and not ISO filesystem constraints or anything.

On Mon, 2005-03-07 at 09:30 +0100, Toralf Lund wrote: >Toralf Lund wrote: > > > >>Felipe Alfaro Solana wrote: >> >> >> >>>On 25 Feb 2005, at 11:19, Toralf Lund wrote: >>> >>> >>> >>>>It seems to me that the question is not whether the file fits into >>>>the DVD, but rather if its size fits into the variables used by >>>>mkisofs to address files and/or doing space calculations. ("mkisofs" >>>>is the command used to actually burn the DVD; k3b is just a >>>>front-end to other commands.) >>>> >>>> >>> >>>No. mkisofs is the program used to create the image, while cdrecord >>>or growisofs is the one used to burn that image. >>> >>> >>Urgh. Minor slip, there."The program used to create the filesystem", I >>meant to say... But my point remains: The problem appears to be >>internal mkisofs limitations, and not ISO filesystem constraints or >>anything. >> >> >Or rather: It may well by an ISO filesystem constraint, but on the size >of one file rather than the total filesystem size. Actually, ISO9660 is >quite likely to have 4Gb max file size... > >- Toralf > > What does ISO9660 and 4gb file size have to do with each other. Iso9660 is a filesystem type. The iso image will be a file on the standard linux filesystem, and its maximum file size is not related to iso9660 standards in amy way. I have not tried mkisofs for some time so it may well have a limitation on filesize it can create, but that would be related to the application and not to the iso9660 limitations. I burn data DVDs regularly from image with more than 4gb of data and never a problem.

Ummmm... come to think of it I do use mkisofs .... I use mondorescue for my backups... that uses mkisofs to create the images for the DVDs

El jue, 24-02-2005 a las 08:06 -0600, Jeff Vian escribió: >On Thu, 2005-02-24 at 14:12 +0100, A. Lanza wrote: > >>Hi list, >> >>i'm trying to burn a DVD using k3b, as i usually do for CD burning. I'm >>using 4,7GB size DVD-R. The problem is that i cannot burn a 4,4GB. file. >>The file is exactly 4,613,704,668 bytes long. >> >>The message i get from k3b is the following: >> /usr/bin/mkisofs: Value too large for defined data type >>and then >> File <file> is too large - ignoring >> >>It seems like the problem is the file size, but that file should fit in >>a DVD, shouldn't it? Is there any limit in the size of files written to >>DVD? >> >>Thanks, >> >>Alf >> > >I create a data DVD by using { file -> new project -> new data DVD >project } then creating the file list to be included with drag-n-drop. > Yes, i'm doing just that way. In fact, when i drag and drop the files, the bar indicating space occupied on the DVD remains in the green zone, doesn't reach the DVD limit.

>On Thu, 2005-02-24 at 14:12 +0100, A. Lanza wrote: >>>i'm trying to burn a DVD using k3b, as i usually do for CD burning. I'm >>>using 4,7GB size DVD-R. The problem is that i cannot burn a 4,4GB. file. >>>The file is exactly 4,613,704,668 bytes long. >>> >>>The message i get from k3b is the following: >>> /usr/bin/mkisofs: Value too large for defined data type >>>and then >>> File <file> is too large - ignoring

Remember that when you burn a file to a DVD, growisofs has to convert the file to an ISO filesystem image and then burn this to the DVD. This process is adding to the number of bytes making the image too large for the disk. Perhaps K3B's size calculation needs some adjustment to account for this size expansion ???

Brian Ashe wrote: > And from the growisofs man page... > > -overburn Normally DVD media can accommodate up to approximately > 4.700.000.000 bytes (in marketing speech 4.7GB). In other words a DVD > can contain about 4.377 GiB or 4482 MiB. Growisofs won't start without > this option, if "overburn" condition appears to be unavoidable. > Bingo! And "-overburn" doesn't seem to be available as a DVD burning option in K3B.

James McKenzie wrote: > John Wendel wrote: > >> Brian Ashe wrote: >> >>> And from the growisofs man page... >>> >>> -overburn Normally DVD media can accommodate up to approximately >>> 4.700.000.000 bytes (in marketing speech 4.7GB). In other words a DVD >>> can contain about 4.377 GiB or 4482 MiB. Growisofs won't start >>> without this option, if "overburn" condition appears to be unavoidable. >>> >> >> Bingo! And "-overburn" doesn't seem to be available as a DVD burning >> option in K3B. > > > Found the overburn selection. Look at Tools -> Configure K3b.... Once > the Options - K3b dialog window opens, look at the Advanced tab under > Writing. There is a selection to allow overburning. This should be > what you are looking for. Nice catch. Thanks!