From: Padraig Brady <padraig.brady@corvil.com>
To: Jesse Pollard <pollard@admin.navo.hpc.mil>
Cc: Larry McVoy <lm@bitmover.com>, Jeff Garzik <jgarzik@pobox.com>,
Phillip Lougher <phillip@lougher.demon.co.uk>,
Samuel Flory <sflory@rackable.com>,
linux-kernel@vger.kernel.org,
Denis Richard <dri@sxb.bsf.alcatel.fr>
Subject: Re: ANNOUNCEMENT: Squashfs released (a highly compressed filesystem)
Date: Wed, 30 Oct 2002 15:10:01 +0000 [thread overview]
Message-ID: <3DBFF649.9030906@corvil.com> (raw)
In-Reply-To: 200210300853.09342.pollard@admin.navo.hpc.mil
Jesse Pollard wrote:
> On Tuesday 29 October 2002 10:11 pm, Larry McVoy wrote:
>
>>>A r/w compressed filesystem would be darned useful too :)
>>
>>mmap(2) is, err, hard. Not impossible, it means the file system has to
>>support both compressed and uncompressed files, but it's interesting.
>
> You can also think of it as a step toward a hierarchical filesystem with the
> files:
> 1. uncompressed (with uncompressed inode)
> 2. compressed on line (real disk space allocated)
> 3. compressed nearline (only compressed inode on disk, with a
> reference to offline storage)
>
> Obviously this is only for very large filesystems (we have one FS that
> is currently between 100-200 TB in size when you include the migrated
> storage).
I think it's worth referencing e2compr here also,
which is a patch that provides transparent compression
for ext2 (& ext3?). Denis RICHARD (CC'd) is maintaining
the 2.4 implementation. I've version 0.4.42 (against
2.4.16) mirrored here:
http://www.iol.ie/~padraiga/patches/e2compr-0.4.42-patch-2.4.16.gz
Note I've used it without problems (to access filesystems
created with the kernel 2.2 version) here:
http://cvs.bofh.asn.au/e2compr/
Pádraig.
next prev parent reply other threads:[~2002-10-30 15:06 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 [this message]
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
-- 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=3DBFF649.9030906@corvil.com \
--to=padraig.brady@corvil.com \
--cc=dri@sxb.bsf.alcatel.fr \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=phillip@lougher.demon.co.uk \
--cc=pollard@admin.navo.hpc.mil \
--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