public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Q: large files in iso9660 ?
Date: Tue, 3 Feb 2004 23:10:23 +0200	[thread overview]
Message-ID: <200402032310.23609.p_christ@hol.gr> (raw)
In-Reply-To: <20040203133551.GA11957@bitwizard.nl>

>
> 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

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..

  reply	other threads:[~2004-02-03 21:11 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
2004-02-03 21:10   ` P. Christeas [this message]
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=200402032310.23609.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox