mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>, plougher@acm.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: Squashfs released (a highly compressed filesystem)
Date: Thu, 31 Oct 2002 04:08:09 +0000	[thread overview]
Message-ID: <3DC0ACA9.2090807@lougher.demon.co.uk> (raw)
In-Reply-To: <20021030072838.A628@nightmaster.csn.tu-chemnitz.de>

Ingo Oeser wrote:
> On Wed, Oct 30, 2002 at 03:51:50AM +0000, Phillip Lougher wrote:
>
>>File sizes upto 2^32 are supported.
 >
> Why limiting to 2GB? AFAIR you wanted to use a cramfs-like
> filesystem for backups. Are videos and large data bases not worth
> of backing up?
> 

Why are files limited to 4GB? (2^32). Simply because I never
thought anything bigger was needed :-)  Initially files were limited to
2^24 (like cramfs), but because of compressed metadata I thought I could
justify an extra 8 bits in the inode, in consideration of the
extra functionality.

Going from 32 bits to 40 bits say is a bigger jump - an extra
2 bytes per file inode (1 byte for the extra file size, and 1
byte because the file start block pointer must increase
by 1 byte as well).  Considering the fact I've tried to squeeze
every last byte out...

However, I could add the extra two bytes if people thought
it was worth it.

Alternatively,  squashfs uses different inodes per file type.  I could
add an extra "big file" type to deal with files bigger than 4GB.  This
would mean > 4GB files are supported, with only one extra byte per inode
for smaller files.  I'll think about it...

> It seems to be good work. So I really wait for Al Viros comments ;-)

Thanks!

Phillip

> Regards
> 
> Ingo Oeser



  reply	other threads:[~2002-10-31  4:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  2:29 Phillip Lougher
2002-10-30  3:10 ` Samuel Flory
2002-10-30  3:51   ` Phillip Lougher
2002-10-30  4:03     ` Jeff Garzik
2002-10-30  4:11       ` Larry McVoy
2002-10-30  4:15         ` Jeff Garzik
2002-10-30 14:53         ` Jesse Pollard
2002-10-30 15:10           ` Padraig Brady
2002-10-30 15:42             ` Denis RICHARD
2002-10-31 16:18               ` Nicholas Wourms
2002-10-30 23:56       ` Phillip Lougher
2002-11-01 15:57         ` Rob Landley
2002-11-02  8:57           ` Phillip Lougher
2002-10-30  6:28     ` Ingo Oeser
2002-10-31  4:08       ` Phillip Lougher [this message]
2002-10-30 14:17 Matthew Wilcox
2002-10-31  5:12 Phillip Lougher

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=3DC0ACA9.2090807@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plougher@acm.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

all inboxes | Powered by JetHome®