mkisofs: Value too large for defined data type.

[Paul Smith]

On 12/8/06, Mikkel L. Ellertson <mikkel at infinity-ltd.com> wrote:
> > I am trying to create an iso file with the command mkisofs, but
> > getting the following problem:
> >
> > $ mkisofs -r -R -J -l -L -max-iso9660-filenames -V "ISOS 22" -o
> > ~/Desktop/isos22.iso .
> > mkisofs: The option '-L' is reserved by POSIX.1-2001.
> > mkisofs: The option '-L' means 'follow all symbolic links'.
> > mkisofs: Mkisofs-2.02 will introduce POSIX semantics for '-L'.
> > mkisofs: Use -allow-leading-dots in future to get old mkisofs behavior.
> > Warning: creating filesystem that does not conform to ISO-9660.
> > Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in
> > the OS.
> > INFO:   ISO-8859-1 character encoding detected by locale settings.
> >        Assuming ISO-8859-1 encoded filenames on source filesystem,
> >        use -input-charset to override.
> > mkisofs: Value too large for defined data type. File ./myfile.iso is
> > too large - ignoring
> >
> > myfile.iso is a 4,1GB file.
> >
> > Any ideas?
> >
> The problem is in the ISO9660 file system specifications. There is a
> file size limit of 2GB. There is supposed to be a way to split up a
> file into multiple extents, each not exceeding the 2 GB limit, but I
> do not know how to do it with mkisofs.

The 2GB limitation does not exist for udf format. However,

$ mkisofs -udf -V "ISOS 22" -o ~/Desktop/isos22.iso .
INFO:   ISO-8859-1 character encoding detected by locale settings.
        Assuming ISO-8859-1 encoded filenames on source filesystem,
        use -input-charset to override.
mkisofs: Value too large for defined data type. File ./myisofile.iso
is too large - ignoring

Paul