View previous topic :: View next topic |
Author |
Message |
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Sat Oct 21, 2006 12:00 pm Post subject: How to burn a >4GB file on a dvd? |
|
|
When I try to burn I get the following error:
Code: | mkisofs: Value too large for defined data type. File /mnt/backups/stage4/belkin2-stage4-2006.10.21-custom.tar.gz_a is too large - ignoring
|
And it fails
Thanks |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Sat Oct 21, 2006 12:21 pm Post subject: |
|
|
It also fails with this:
Code: |
cp /mnt/backups/stage4/belkin2-stage4-2006.10.21-custom.tar.gz_a /mnt/iso/.
File size limit exceded
|
Thanks |
|
Back to top |
|
|
RiBBiT Apprentice
Joined: 18 May 2005 Posts: 215 Location: Sweden
|
Posted: Sat Oct 21, 2006 10:21 pm Post subject: |
|
|
The filesystem commonly used on CDs (and DVDs) is called ISO 9660 and only support files smaller than 2 GB. You should instead use the UDF filesystem which supports much larger files. _________________ Comix - GTK Comic Book Viewer [ http://comix.sourceforge.net ] |
|
Back to top |
|
|
vibrokatana Guru
Joined: 09 Feb 2006 Posts: 328 Location: o0o0oo
|
Posted: Sun Oct 22, 2006 7:58 am Post subject: |
|
|
You could also use the split command, not really the best solution tho. _________________ My Systems - "I suggest the whole thing be coded in whitespace. Henceforth the code will be obscure and functional at the same time." |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Sun Oct 22, 2006 10:16 am Post subject: |
|
|
RiBBiT wrote: | The filesystem commonly used on CDs (and DVDs) is called ISO 9660 and only support files smaller than 2 GB. You should instead use the UDF filesystem which supports much larger files. |
How can I use UDF filesystem for recording this files?
growisofs -udf... doesn't work form me
Thanks a lot |
|
Back to top |
|
|
Kraymer Guru
Joined: 27 Aug 2003 Posts: 349 Location: Germany
|
Posted: Mon Oct 23, 2006 12:00 pm Post subject: |
|
|
pacho2 wrote: | How can I use UDF filesystem for recording this files?
growisofs -udf... doesn't work form me |
Creating udf filesystem is not a method/property of burning but of creating the iso image you are going to burn. Use -udf with mkisofs. |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Mon Oct 23, 2006 12:04 pm Post subject: |
|
|
Kraymer wrote: | Use -udf with mkisofs. |
It also fails with the same error |
|
Back to top |
|
|
Kraymer Guru
Joined: 27 Aug 2003 Posts: 349 Location: Germany
|
Posted: Mon Oct 23, 2006 12:09 pm Post subject: |
|
|
pacho2 wrote: | Kraymer wrote: | Use -udf with mkisofs. |
It also fails with the same error |
Please post you command line.
Also, have you verified that your kernel supports udf? |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Mon Oct 23, 2006 8:06 pm Post subject: |
|
|
Mi /proc/config.gz:
Code: |
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
|
And output:
Code: |
growisofs -udf -Z /dev/hdc fichero-grande
WARNING: /dev/hdc already carries isofs!
About to execute 'mkisofs -udf fichero-grande | builtin_dd of=/dev/hdc obs=32k seek=0'
mkisofs: Value too large for defined data type. File fichero-grande is too large - ignoring
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 21000
417 extents written (0 MB)
/dev/hdc: "Current Write Speed" is 4.1x1352KBps.
builtin_dd: 432*2KB out @ average 0.1x1352KBps
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out
|
Thanks |
|
Back to top |
|
|
kf0yn Tux's lil' helper
Joined: 25 Jan 2003 Posts: 84
|
Posted: Wed Oct 25, 2006 8:19 pm Post subject: |
|
|
Even with the -udf flag, mkisofs still generates the ISO9660 file system. There's no way to use mkisofs to put a >4GB file in a filesystem.
I don't know of any tools that will do it, but that doesn't mean they don't exist. |
|
Back to top |
|
|
Kraymer Guru
Joined: 27 Aug 2003 Posts: 349 Location: Germany
|
Posted: Wed Oct 25, 2006 8:36 pm Post subject: |
|
|
Hm, I'm sorry I couldn't really help here.
But if the problem lies in ISO9660, maybe creating only rockridge (-R I think) will do it. Disc won't be readable in windows then though. |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Wed Oct 25, 2006 8:43 pm Post subject: |
|
|
Same problem
Code: |
growisofs -udf -R -Z /dev/hdc fichero-grande
WARNING: /dev/hdc already carries isofs!
About to execute 'mkisofs -udf -R fichero-grande | builtin_dd of=/dev/hdc obs=32k seek=0'
mkisofs: Value too large for defined data type. File fichero-grande is too large - ignoring
Total translation table size: 0
Total rockridge attributes bytes: 169
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 21000
418 extents written (0 MB)
/dev/hdc: "Current Write Speed" is 4.1x1352KBps.
builtin_dd: 432*2KB out @ average 0.1x1352KBps
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out
|
If I don't use -udf option:
Code: |
growisofs -R -Z /dev/hdc fichero-grande
WARNING: /dev/hdc already carries isofs!
About to execute 'mkisofs -R fichero-grande | builtin_dd of=/dev/hdc obs=32k seek=0'
mkisofs: Value too large for defined data type. File fichero-grande is too large - ignoring
Total translation table size: 0
Total rockridge attributes bytes: 169
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 21000
175 extents written (0 MB)
/dev/hdc: "Current Write Speed" is 4.1x1352KBps.
builtin_dd: 176*2KB out @ average infx1352KBps
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out
|
Thanks a lot |
|
Back to top |
|
|
RiBBiT Apprentice
Joined: 18 May 2005 Posts: 215 Location: Sweden
|
Posted: Wed Oct 25, 2006 8:56 pm Post subject: |
|
|
I use k3b to burn large files successfully. This is the mkisofs command it spits out, most of it is probably redundant though:
Code: |
mkisofs command:
-----------------------
/usr/bin/mkisofs -gui -graft-points -volid DVD data disc -volset -appid -publisher -preparer -sysid Linux -volset-size 1 -volset-seqno 1 -sort /tmp/kde-sork/k3bLDR0Qa.tmp -rational-rock -hide-list /tmp/kde-sork/k3btrYkja.tmp -joliet -hide-joliet-list /tmp/kde-sork/k3bdOMpXa.tmp -udf -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-sork/k3b4638Xa.tmp
|
_________________ Comix - GTK Comic Book Viewer [ http://comix.sourceforge.net ] |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Thu Oct 26, 2006 7:49 am Post subject: |
|
|
I have tried this:
Code: |
growisofs -udf -gui -volset -graft-points -appid -publisher -preparer -rational-rock -joliet -full-iso9660-filenames -iso-level 2 -Z /dev/dvd belkin-stage4-2006.09.22-custom.tar.gz_a
WARNING: /dev/dvd already carries isofs!
About to execute 'mkisofs -udf -gui -volset -graft-points -appid -publisher -preparer -rational-rock -joliet -full-iso9660-filenames -iso-level 2 belkin-stage4-2006.09.22-custom.tar.gz_a | builtin_dd of=/dev/dvd obs=32k seek=0'
Warning: creating filesystem with (nonstandard) Joliet extensions
but without (standard) Rock Ridge extensions.
It is highly recommended to add Rock Ridge
mkisofs: Value too large for defined data type. File belkin-stage4-2006.09.22-custom.tar.gz_a is too large - ignoring
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 21000
422 extents written (0 MB)
/dev/dvd: "Current Write Speed" is 4.1x1385KBps.
builtin_dd: 432*2KB out @ average infx1385KBps
/dev/dvd: flushing cache
/dev/dvd: stopping de-icing
/dev/dvd: writing lead-out
/dev/dvd: reloading tray
|
And it fails
Thanks a lot |
|
Back to top |
|
|
RiBBiT Apprentice
Joined: 18 May 2005 Posts: 215 Location: Sweden
|
Posted: Thu Oct 26, 2006 10:50 am Post subject: |
|
|
Are you sure the DVD is blank? It looks as if you are trying to burn a used disc, this is the clue:
Code: | WARNING: /dev/dvd already carries isofs! |
_________________ Comix - GTK Comic Book Viewer [ http://comix.sourceforge.net ] |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Thu Oct 26, 2006 8:06 pm Post subject: |
|
|
RiBBiT wrote: | Are you sure the DVD is blank? It looks as if you are trying to burn a used disc, this is the clue:
Code: | WARNING: /dev/dvd already carries isofs! |
|
It is a DVD+RW, this is the normal behavior
Thanks |
|
Back to top |
|
|
vibrokatana Guru
Joined: 09 Feb 2006 Posts: 328 Location: o0o0oo
|
Posted: Thu Oct 26, 2006 8:08 pm Post subject: |
|
|
You have to blank it... _________________ My Systems - "I suggest the whole thing be coded in whitespace. Henceforth the code will be obscure and functional at the same time." |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Thu Oct 26, 2006 8:24 pm Post subject: |
|
|
vibrokatana wrote: | You have to blank it... |
DVD+RW drives don't have to be blanked, they work fine with "small" files, I only have problems with big files.
Thanks |
|
Back to top |
|
|
vibrokatana Guru
Joined: 09 Feb 2006 Posts: 328 Location: o0o0oo
|
Posted: Thu Oct 26, 2006 8:29 pm Post subject: |
|
|
wow some people are hard headed... _________________ My Systems - "I suggest the whole thing be coded in whitespace. Henceforth the code will be obscure and functional at the same time." |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Thu Oct 26, 2006 8:33 pm Post subject: |
|
|
vibrokatana wrote: | wow some people are hard headed... |
DVD+RW drives DON'T HAVE TO BE BLANKED
Is there any "special" blanking that only affects to big files recording?
From http://fy.chalmers.se/~appro/linux/DVD+RW/
Quote: | Formatting the BD and DVD+RW media. Virgin BD and DVD+RW media needs to be initally formatted prior usage. Once again, only virgin BD and DVD+RW media needs to be formatted. As of version 5.10 growisofs detects blanks and applies initial formatting procedure automatically. Otherwise same effect can be achieved by passing the device name, e.g. /dev/scd0, as an argument to dvd+rw-format. Well, in BD case it does offer more flexibility than growisofs. To make formatting process reasonably fast, less than 1 minute, the media gets formatted only partially, as you can notice by observing progress indicator displayed by dvd+rw-format. The final indicator value varies from firmware to firmware, values as low as 1.6% were observed. But it does not mean that you can only write that little. The unit keeps formatting transparently, as you add more data. Oh! Do keep in mind that DVD capacity of 4.7GB is expressed in salesman's GB, i.e. 10003 and not 10243. And so is one of BD.
It was observed that excessive reformats can render DVD+RW media unusable already after 10-20 reformats. It appears to be a firmware deficiency, not some common media defect [at least it was perfectly possible to salvage the media in a unit of different brand], but I don't recommend [enforced] reformat in either case.
Note that re-formatting procedure does not substitute for blanking. If you want to nullify the media, e.g. for privacy reasons, do it explicitly with 'growisofs -Z /dev/scdN=/dev/zero'. Otherwise just write over previous recording as it simply wasn't there, no re-formatting is required. |
Thanks a lot for trying to help me |
|
Back to top |
|
|
Rad Guru
Joined: 11 Feb 2004 Posts: 401 Location: Bern, Switzerland
|
Posted: Fri Oct 27, 2006 12:21 pm Post subject: |
|
|
Right, they don't have to be blanked.
Back on topic, I'm not sure what exactly mkisofs does when you specify the "-udf" option, but according to it's man page, mkisofs can't create an udf only image. I sorta guess the other part of the hybrid is always some sort of iso9660 filesystem, and you never will get around it with mkisofs...
If that's true, you have to use some other program to create a real UDF DVD. I only know mkudffs for that.
Now, if your burner supports it: By any means, use DVD-RAM; they're safer, more suitable for frequent rewrites, and they can be treated just like hard disk drives (just format and use them, no creating images or anything required!)
Anyways, there's also at least two ways of using DVD-+RW/R and UDF.
The more elegant one would be to use packet writing; it does some tricks to get similar writing to regular CD or DVD media as DVD-RAM or hard disk drives physically have. This tutorial should help.
If that doesn't work for some reason, you can always create your udf filesystem on your hard disk drive first (inside a regular, loopback mounted file if you have no free space for an additional partition), mount it, copy your data there, and then write the partition on your dvd. Instructions for that can be found in this thread. |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
|
Back to top |
|
|
Rad Guru
Joined: 11 Feb 2004 Posts: 401 Location: Bern, Switzerland
|
Posted: Fri Oct 27, 2006 1:08 pm Post subject: |
|
|
I can imagine why the second post you linked doesn't work since there the image there would be too small (only 200000 bytes), but I have no idea why it shouldn't work when you do it according to the first post. Is the error message the same? Is your image file on disk really large enough (try "df -h" and compare with your backup...)?
About using /dev/dvd directly... you say it worked without explicitly setting it up for packet writing, but just didn't take any file larger than 1GB? |
|
Back to top |
|
|
pacho2 Developer
Joined: 04 Mar 2005 Posts: 2599 Location: Oviedo, Spain
|
Posted: Fri Oct 27, 2006 1:15 pm Post subject: |
|
|
Rad wrote: | I can imagine why the second post you linked doesn't work since there the image there would be too small (only 200000 bytes), but I have no idea why it shouldn't work when you do it according to the first post. Is the error message the same? Is your image file on disk really large enough (try "df -h" and compare with your backup...)?
About using /dev/dvd directly... you say it worked without explicitly setting it up for packet writing, but just didn't take any file larger than 1GB? |
The size of img created is 2GB, but (I don't know why) I cannot copy on it files larger than 1GB
Thanks |
|
Back to top |
|
|
|