From: Vladimir Saveliev <vs@namesys.com>
To: "P. Christeas" <p_christ@hol.gr>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Q: large files in iso9660 ?
Date: Wed, 04 Feb 2004 10:43:28 +0300 [thread overview]
Message-ID: <1075880608.1830.108.camel@tribesman.namesys.com> (raw)
In-Reply-To: <200402032310.23609.p_christ@hol.gr>
Hello
On Wed, 2004-02-04 at 00:10, P. Christeas wrote:
> >
> > 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..
IIRC, mkisofs can create HFS. There should be no problem with that long
files
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-02-04 7:43 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
2004-02-04 7:43 ` Vladimir Saveliev [this message]
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=1075880608.1830.108.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p_christ@hol.gr \
/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