From: Erik Mouw <erik@harddisk-recovery.com>
To: "P. Christeas" <p_christ@hol.gr>
Cc: lkml <linux-kernel@vger.kernel.org>, viro@math.psu.edu
Subject: Re: Q: large files in iso9660 ?
Date: Tue, 3 Feb 2004 14:35:51 +0100 [thread overview]
Message-ID: <20040203133551.GA11957@bitwizard.nl> (raw)
In-Reply-To: <200402020024.31785.p_christ@hol.gr>
On Mon, Feb 02, 2004 at 12:24:31AM +0200, P. Christeas wrote:
> 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.
> 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.
> 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 schilling@fokus.gmd.de
*/
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
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2004-02-03 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 22:24 Q: large files in iso9660 ? P. Christeas
2004-02-03 13:35 ` Erik Mouw [this message]
2004-02-03 21:10 ` P. Christeas
2004-02-04 7:43 ` Vladimir Saveliev
2004-02-04 8:51 ` Eduard Bloch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040203133551.GA11957@bitwizard.nl \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p_christ@hol.gr \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.