mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Nicolas.Turro@sophia.inria.fr
Subject: Re: any compressed filesystem suggestion ?
Date: Tue, 04 Feb 2003 02:27:13 +0000	[thread overview]
Message-ID: <3E3F2501.9070009@lougher.demon.co.uk> (raw)

Nicolas Turro wrote:
 >
 >Hi, we plan to build an NFS archive of old unix close accounts, and we 
are
 >looking for a compressed filesystem since size is more important than 
 >speed  for us. Our requirements are :
 >1- this fs must run on hardware raid (DAC960  Mylex AcceleRAID)
 >2- the archives files will be read-only for users, but we 
 >(administrators)
 >must be able to add files to the archives...
 >
 >Any recomendations ?

 >squashfs doesn't qualify because of 2 ...

Hi,

Append capability is the thing I'm currently adding to Squashfs.  Once 
finished, you'll be able to add new files/directories to the top level 
directory of a previously created filesystem.  As the mksquashfs program 
performs duplicate file checking against the files in the filesystem as 
well as the files being added, this means it will also work as a kind of 
incremental archiving filesystem.

An initial release should be ready in a week (or two depending on free 
time).

Phillip

 >what about e2compress ? http://www.alizt.com/index.html
 >
 >I've heard about block layer compression... is it applicable for us ?
 >Thanks for your advice...
 >
 >N. Turro


             reply	other threads:[~2003-02-04  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04  2:27 Phillip Lougher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-31 13:51 Nicolas Turro

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=3E3F2501.9070009@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=Nicolas.Turro@sophia.inria.fr \
    --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

all inboxes | Powered by JetHome®