Q: large files in iso9660 ?
Hi,
I've tried to create a disk (DVD) which contains a single 3.8GB file. The creation (mkisofs) worked and the disk's TOC reads 3.8GB. However, the filesystem reads as if one ~9MB file only exists.
I guess large files in isofs may be out of spec.
Q: What's the file size limit in iso9660?
Q: Is there any chance the negative number (although out of spec) may be correctly interpreted (mount option) ?
Thanks.
FYI:
isoinfo -d -i /dev/cdrom
CD-ROM is in ISO 9660 format
System id: LINUX
Volume id: CDROM
Volume set id:
Publisher id:
Data preparer id:
Application id: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR (C) 1993 E.YOUNGDALE (C) 1997 J.PEARSON/J.SCHILLING Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set seqence number is: 1
Logical block size is: 2048
Volume size is: 1987287
Joliet with UCS level 3 found
Rock Ridge signatures version 1 found
isoinfo -l -i /dev/cdrom
Directory listing of /
d--------- 0 0 0 2048 Jan 31 2004 [ 28] . d--------- 0 0 0 2048 Jan 31 2004 [ 28] .. ---------- 0 0 0 -225376141 Jan 31 2004 [ 31] WIN_C.TGZ;1
Quoted 2 lines · P. Christeas
I've tried to create a disk (DVD) which contains a single 3.8GB file. The creation (mkisofs) worked and the disk's TOC reads 3.8GB.
No, it didn't. Last time I tried mkisofs warned about files being larger than 2GB. Feel free to ignore the warnings, though.
Quoted 5 lines
However, the
filesystem reads as if one ~9MB file only exists.
I guess large files in isofs may be out of spec.Q: What's the file size limit in iso9660?
About 2GB.
Quoted 2 lines
Q: Is there any chance the negative number (although out of spec) may be correctly interpreted (mount option) ?
The kernel (2.6 and 2.4) has the following code in isofs_read_inode():
/*
* The ISO-9660 filesystem only stores 32 bits for file size.
* mkisofs handles files up to 2GB-2 = 2147483646 = 0x7FFFFFFE bytes
* in size. This is according to the large file summit paper from 1996.
* WARNING: ISO-9660 filesystems > 1 GB and even > 2 GB are fully
* legal. Do not prevent to use DVD's [email protected]
*/
if ((inode->i_size < 0 || inode->i_size > 0x7FFFFFFE) &&
sbi->s_cruft == 'n') {
printk(KERN_WARNING "Warning: defective CD-ROM. "
"Enabling \"cruft\" mount option.\n");
sbi->s_cruft = 'y';
}IOW: your kernel should have warned you about the defective CDROM and truncated filesizes to 16MB (which is what the "cruft" mount option does).
Erik
Signature · 2 lines
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
Quoted 16 lines
The kernel (2.6 and 2.4) has the following code in
isofs_read_inode():/*
* The ISO-9660 filesystem only stores 32 bits for file size.
* mkisofs handles files up to 2GB-2 = 2147483646 =0x7FFFFFFE
bytes * in size. This is according to the large file summit paper from 1996. * WARNING: ISO-9660 filesystems > 1 GB and even > 2 GB are fully *legal. Do not prevent to use DVD's [email protected] */ if ((inode->i_size < 0 || inode->i_size > 0x7FFFFFFE) && sbi->s_cruft == 'n') { printk(KERN_WARNING "Warning: defective CD-ROM. " "Enabling \"cruft\" mount option.\n"); sbi->s_cruft = 'y'; }
Quoted 6 lines
IOW: your kernel should have warned you about the defective CDROM and truncated filesizes to 16MB (which is what the "cruft" mount option does).
Erik
Makes perfect sense.
However, this *does* enforce the limit on DVD files. If I try to disable this code and make inode sizes uint32, can there be any other negative implication? Of course, I am still limited to 3GB..
Hello
Quoted 21 lines · P. Christeas
Quoted 21 lines
The kernel (2.6 and 2.4) has the following code in
isofs_read_inode():/*
* The ISO-9660 filesystem only stores 32 bits for file size.
* mkisofs handles files up to 2GB-2 = 2147483646 =0x7FFFFFFE
bytes * in size. This is according to the large file summit paper from 1996. * WARNING: ISO-9660 filesystems > 1 GB and even > 2 GB are fully *legal. Do not prevent to use DVD's [email protected] */ if ((inode->i_size < 0 || inode->i_size > 0x7FFFFFFE) && sbi->s_cruft == 'n') { printk(KERN_WARNING "Warning: defective CD-ROM. " "Enabling \"cruft\" mount option.\n"); sbi->s_cruft = 'y'; }IOW: your kernel should have warned you about the defective CDROM and truncated filesizes to 16MB (which is what the "cruft" mount option does).
Quoted 6 lines
Quoted 1 line
Erik
Makes perfect sense.
However, this *does* enforce the limit on DVD files. If I try to disable this code and make inode sizes uint32, can there be any other negative implication? Of course, I am still limited to 3GB..
IIRC, mkisofs can create HFS. There should be no problem with that long files
Quoted 6 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
#include <hallo.h>
Quoted 6 lines · Erik Mouw
Quoted 2 lines · P. Christeas
I've tried to create a disk (DVD) which contains a single 3.8GB file. The creation (mkisofs) worked and the disk's TOC reads 3.8GB.
No, it didn't. Last time I tried mkisofs warned about files being larger than 2GB. Feel free to ignore the warnings, though.
No, normal mkisofs does not warn, are you sure that your distributor did not patch it?
Quoted 7 lines
Quoted 5 lines
However, the
filesystem reads as if one ~9MB file only exists.
I guess large files in isofs may be out of spec.Q: What's the file size limit in iso9660?
About 2GB.
Really? Quoting Joerg Schilling:
| >#include <hallo.h> | >* christophe nowicki [Thu, Jan 22 2004, 01:22:34PM]: | | >> #mount -t iso9660 -o loop burn.iso /mnt | >> $ls -sh /mnt | >> total 4.0M | >> 4.0M test | >> ^ all my data are lost ! | >>=20 | >> During the creation process mkisofs did not make a warning ... | | Definitely wrong (even for the outdated 2.0 version)! | | .... see log below: | | mkdir LD | cd LD | mkfile -n 5g 5g | cd .. | /opt/schily/bin/mkisofs -o /tmp/0a LD | /opt/schily/bin/mkisofs: Value too large for defined data type. File LD/5g 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 8000 | 48 extents written (0 Mb) | | | >Reproducible for me. IMHO it is not only the iso9660 filesize limit, | >since Joliet should support larger files. | | Definitely wrong too: Joliet is a half hearted hack on ISO-9660. | If you like to have large files in ISO-9660 (and/or Joliet!), you would need | multi extent file support. | | In order to implement this, you need an OS to test with.... | | Solaris has no multi extent file support | | Linux fails with several other problems in the vicinity of large files on | ISO-9660 and in such a case auto activates evil mount options that prevents | you from using such media. | | | Jörg
Quoted 9 lines
The kernel (2.6 and 2.4) has the following code in
isofs_read_inode():/*
* The ISO-9660 filesystem only stores 32 bits for file size.
* mkisofs handles files up to 2GB-2 = 2147483646 =0x7FFFFFFEbytes
* in size. This is according to the large file summit paper from 1996.
* WARNING: ISO-9660 filesystems > 1 GB and even > 2 GB are fully
* legal. Do not prevent to use DVD's [email protected]
*/
Interesting, what should be "multiple extents" then?
Quoted 4 lines
if ((inode->i_size < 0 || inode->i_size > 0x7FFFFFFE) &&
sbi->s_cruft == 'n') {
printk(KERN_WARNING "Warning: defective CD-ROM. "
"Enabling \"cruft\" mount option.\n");I have never seen this warning on mounting "defective" filesystems.
Regards,
Eduard.
Signature · 2 lines
Man weist ein Lob zurück in dem Wunsch, nochmals gelobt zu werden. -- François de La Rochefoucauld