public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Samuel Flory <sflory@rackable.com>, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCEMENT: Squashfs released (a highly compressed filesystem)
Date: Wed, 30 Oct 2002 23:56:10 +0000	[thread overview]
Message-ID: <3DC0719A.30101@lougher.demon.co.uk> (raw)
In-Reply-To: 3DBF5A08.9090407@pobox.com

Jeff Garzik wrote:
 > Phillip Lougher wrote:

 >
 >> 2. Squashfs compresses inode and directory information in addition
 >> to file data.  Inodes/directories generally compress down to 50%, or
 >> say on average 8 bytes or less per inode.
 >
 >
 > squashfs or mksquashfs?

mksquashfs...

 >
 > A r/w compressed filesystem would be darned useful too :)
 >
 > Jeff
 >

A r/w compressed filesystem may be my next project...  As a couple of
people have mentioned there are compressed r/w filesystems already
out there.

As you'll know, there are always tradeoffs with filesystem design,
it is very difficult to get as good compression with a r/w fs
than with a read only filesystem.  I wanted to get maximum
compression, and quite a few of the techniques I use rely on
its read-only nature.

An append only (i.e. files can be added, but not modified), fs might
be a useful compromise.  With compressed metadata, any modification
of files will inevitably achive different compression ratios, and so
modification of metadata/files in place is not an option.  Appending
modified metadata/data brings you to log-structured (journalling)
filesystems and compaction (log cleaning) requirements with consequent
loss of compression.

Phillip


 >
 >
 >
 >




  parent reply	other threads:[~2002-10-30 23:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  2:29 ANNOUNCEMENT: Squashfs released (a highly compressed filesystem) 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=3DC0719A.30101@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    /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