public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compressed Filesystem
Date: Tue, 29 Dec 2009 14:04:15 +0100	[thread overview]
Message-ID: <200912291404.15508.volkerarmin@googlemail.com> (raw)
In-Reply-To: <tkrat.2087f50fbc3d470a@igpm.rwth-aachen.de>

On Dienstag 29 Dezember 2009, Helmut Jarausch wrote:
> On 28 Dec, Volker Armin Hemmann wrote:
> > On Montag 28 Dezember 2009, Helmut Jarausch wrote:
> >> Hi,
> >>
> >> I'm looking for a working and maintained compressed filesystem.
> >> I'd like to use it for backing up my root and my /usr filesystems,
> >> so that I can use rsync to keep it up-to-date.
> >>
> >> I've come across CompFused which seems to be just what I'm looking for,
> >> but it's buggy not maintained anymore.
> >>
> >> Similarly, fusecompress
> >> http://bugs.gentoo.org/show_bug.cgi?id=127433
> >> doesn't build on an up-to-date Gentoo system and doesn't
> >> look maintained either.
> >>
> >> There would be sys-fs/zfs-fuse but that sounds like overkill to me.
> >>
> >> Are there any other packages?
> >>
> >> Many thanks for a hint,
> >> Helmut.
> >
> > reiser4. Bonus, it only tries to compress stuff that can be compressed
> > (the test is quick&dirty and sometimes wrong, but most of the time good
> > enough).
> 
> Thanks!
> But what's the future of reiser4 FS ? What are the advantages compared
> to btrfs ?

reiser4 was denied for 'layer violation'.
btrfs violates those layers even more.

I do no know btrfs. But there are two nice things about reiser4:
it takes your data seriously. It tries everything to make sure your data hit 
the platter. Device does not support barriers? Reiser4 detects that and goes 
into sync mode.
Second, reiser4 is really, really really fast (except mounting).



  reply	other threads:[~2009-12-29 13:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28 11:58 [gentoo-user] Compressed Filesystem Helmut Jarausch
2009-12-28 12:10 ` Mike Kazantsev
2009-12-28 12:29 ` William Kenworthy
2009-12-28 18:44 ` Volker Armin Hemmann
2009-12-29  8:31   ` Helmut Jarausch
2009-12-29 13:04     ` Volker Armin Hemmann [this message]
2009-12-29 23:01       ` Stefan G. Weichinger
2009-12-29 23:08         ` Volker Armin Hemmann
2009-12-30  0:17           ` Albert Hopkins
2009-12-30  0:45             ` Volker Armin Hemmann
2009-12-30 13:48             ` Stroller
2009-12-30 14:12             ` Marcus Wanner
2009-12-30 14:20               ` Volker Armin Hemmann
2009-12-31  1:04               ` Neil Bothwick
2009-12-31  2:57                 ` Marcus Wanner
2009-12-31  4:18                   ` Dale
2009-12-31  8:20                     ` Volker Armin Hemmann
2009-12-31 16:54                       ` Marcus Wanner
2009-12-31 17:20                       ` Dale
2009-12-30  9:20           ` Stefan G. Weichinger
2010-01-03  6:35 ` Enrico Weigelt
2010-01-03 11:53   ` Helmut Jarausch
2010-01-03 13:48     ` Mike Kazantsev
2010-02-06  0:03     ` Enrico Weigelt
  -- strict thread matches above, loose matches on Subject: below --
2011-08-31 15:50 [gentoo-user] compressed filesystem Space Cake
2011-08-31 16:21 ` Nilesh Govindarajan
2011-08-31 16:23   ` Nilesh Govindarajan
2011-08-31 23:37   ` Adam Carter
2011-09-01  7:04     ` Bill Kenworthy
2011-09-01  7:13       ` Adam Carter
2011-09-01  8:01         ` Bill Kenworthy

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=200912291404.15508.volkerarmin@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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