Re: problems writing a large file to DVD+R Double Layer disk
Dominique Dumont
> I am trying to write a .ts file to a DVD+R Double Layer disk, so far
> without success. The file has a size of 4613734320. I issue the
> command:
>
> growisofs -Z /dev/sr1 -R -J pd
I currently create an udf image with genisofs:
# -r : Rock ridge avec des perm uid et gid correct
# -allow-limited-size: requis pour des fichiers > 2GB
# -f: follow sym link (pas de symlink avec udf)
genisoimage -udf -f -r -J -allow-limited-size -o ~/dvd.iso *
Then I burn the image with growisofs -Z /dev/hda=dvd.iso
When you mount the cd, be sure to mount it as udf:
mount -t udf /dev/hda /media/cdrom0
You can probably create the image directly while running growisofs,
but I have not tried yet.
HTH
--
To UNSUBSCRIBE, email to cdwrite...@other.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@other.debian.org
Joerg Schilling
> Kish Shen <kish...@crosscoreop.com> writes:
>
> > I am trying to write a .ts file to a DVD+R Double Layer disk, so far
> > without success. The file has a size of 4613734320. I issue the
> > command:
> >
> > growisofs -Z /dev/sr1 -R -J pd
>
> I currently create an udf image with genisofs:
What do you expect from using an unmaintained fork from a > 2.5 year old
version of mkisofs?
If you decouple yourself from the original software, you get decoupled
from bugfixes and enhancements. Note that your old version misses
147 enhancements and bugfixes. Several dozens of bugs have been fixed that
origin in the very early years of mkisofs (past 1993). Using old versions
of software is never a good idea.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
schi...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Joerg Schilling
> Joerg.S...@fokus.fraunhofer.de (Joerg Schilling) writes:
>
> >> I currently create an udf image with genisofs:
> >
> > What do you expect from using an unmaintained fork from a > 2.5 year old
> > version of mkisofs?
>
> Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file
> with it.
Well, I did add large file support to mkisofs on January 25th 2001.
Dou you like to use a 6+ year old program? Obviously not, so why to you
use a nearly 3 year old program?
If you like to benefit from development efforts, you should upgrade
to a recent version from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
This is where you may also find a complete list of all enhencements and
bugfixes since September 2004, the origin of your fork....
Ismail Dönmez
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sunday 29 April 2007 14:18:34 Joerg Schilling wrote:
> Dominique Dumont <domi....@free.fr> wrote:
> > Joerg.S...@fokus.fraunhofer.de (Joerg Schilling) writes:
> > >> I currently create an udf image with genisofs:
> > >
> > > What do you expect from using an unmaintained fork from a > 2.5 year
> > > old version of mkisofs?
> >
> > Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file
> > with it.
>
> Well, I did add large file support to mkisofs on January 25th 2001.
Hmm but you said mkisofs would support such large files in a later date? Or=
=20
did I get it all wrong?
Regards,
ismail
--nextPart2743656.jZjGN1pULC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
iD8DBQBGNH/yGp0leluI9UwRAqXpAJ4tLbZf9iCCraVpNav4iHT0SxomTgCfeQdQ
MplUJiFrrj+BVY1V0eMlpbw=
=MmLf
-----END PGP SIGNATURE-----
--nextPart2743656.jZjGN1pULC--
Joerg Schilling
> > > > What do you expect from using an unmaintained fork from a > 2.5 year
> > > > old version of mkisofs?
> > >
> > > Well, it may be 2.5 years old, but I managed to burn a 7.4 GB file
> > > with it.
> >
> > Well, I did add large file support to mkisofs on January 25th 2001.
>
> Hmm but you said mkisofs would support such large files in a later date? Or
> did I get it all wrong?
Seems you did get things wrong.
Mkisofs theorectically writes ISO image files up to 16 Exabytes. The size of an
ISO image is technically limited (by the ISO-9660 filesystem) to 8 Terabytes.
A 7.4 GB filesystem is more than 1000x smaller than what ISO-9660 supports.
Mkisofs supports single UDF files > 1 GB (up to 234 GB) since November 24th 2002
If you turn off consistency checks, you may write defective ISO images that
seem to include single files larger than 4 GB since then.
In a few weeks, mkisofs will support single files up to 8 TB and hide these files
(if larger tan 234 GB) from the UDF tree for consistency.
Mkisofs development is oriented on quality and reliability rather than
implementing cheep hacks.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
schi...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Ismail Dönmez
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sunday 29 April 2007 15:31:35 Joerg Schilling wrote:
[...]
> Seems you did get things wrong.
>
> Mkisofs theorectically writes ISO image files up to 16 Exabytes. The size
> of an ISO image is technically limited (by the ISO-9660 filesystem) to 8
> Terabytes.
>
> A 7.4 GB filesystem is more than 1000x smaller than what ISO-9660 support=
s.
>
> Mkisofs supports single UDF files > 1 GB (up to 234 GB) since November 24=
th
> 2002 If you turn off consistency checks, you may write defective ISO imag=
es
> that seem to include single files larger than 4 GB since then.
>
> In a few weeks, mkisofs will support single files up to 8 TB and hide the=
se
> files (if larger tan 234 GB) from the UDF tree for consistency.
So the problem is that currently a file that is larger than 4GB is not=20
supported but if the files are smaller than 4 GB there is no problem with=20
writing a 7.4 GB isofile ?
Regards,
ismail
--nextPart1254606.dkFLRXz9qu
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
iD8DBQBGNJGyGp0leluI9UwRArGXAJ9+PVj9EjmGGBmQJcNJv+82M5QxmwCeOmVl
5mkORf+2/jnion5uZEIEo4Y=
=2Z+1
-----END PGP SIGNATURE-----
--nextPart1254606.dkFLRXz9qu--
Joerg Schilling
> > In a few weeks, mkisofs will support single files up to 8 TB and hide these
> > files (if larger tan 234 GB) from the UDF tree for consistency.
>
> So the problem is that currently a file that is larger than 4GB is not
> supported but if the files are smaller than 4 GB there is no problem with
> writing a 7.4 GB isofile ?
Files in the ISO-9660 namespace are not yet supported to be > 4 GB.
This will change soon.
Note that as this "genisoimage" fork is based on an old version of mkisofs, it
does not support more than a recent mkisofs.
Jörg
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
schi...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Ismail Dönmez
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Sunday 29 April 2007 16:15:50 you wrote:
> Ismail D=F6nmez <ism...@pardus.org.tr> wrote:
> > > In a few weeks, mkisofs will support single files up to 8 TB and hide
> > > these files (if larger tan 234 GB) from the UDF tree for consistency.
> >
> > So the problem is that currently a file that is larger than 4GB is not
> > supported but if the files are smaller than 4 GB there is no problem wi=
th
> > writing a 7.4 GB isofile ?
>
> Files in the ISO-9660 namespace are not yet supported to be > 4 GB.
>
> This will change soon.
That clears up everything for me. Thanks for taking time to explain.
Best Regards,
ismail
--nextPart1381235.sNpfZNY5AM
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
iD8DBQBGNJ8OGp0leluI9UwRAhQtAJ9ogUGNwioF0jPoY7x5jclayFi6xACfXRXp
buTHPjuhB39Yl4Yc0GqdBtE=
=Bk5K
-----END PGP SIGNATURE-----
--nextPart1381235.sNpfZNY5AM--