Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>,
	"BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Another defrag question
Date: Thu, 21 Feb 2013 18:47:28 +0100	[thread overview]
Message-ID: <51265DB0.2060407@petaramesh.org> (raw)
In-Reply-To: <20130221172502.GF14283@carfax.org.uk>

Le 21/02/2013 18:25, Hugo Mills a écrit :
> Correct. But btrfs isn't at that stage yet. It's getting visibly
> closer, but it's not quite there. Hence the very strong recommendation
> to keep up with the latest code. Hugo. 

The matter is that BTRFS had many early adopters just because it is -
and has been for long now - in the mainline Linux kernel, so supposed
stable and good choice for the future.

To be honest (and not wanting to troll, promised) this is the only
single reason for which I use BTRFS on 5 of my 6 machines at home - just
because I thought that "Just upgrade the distro every 6 months and it
will become better and better over time, no hassle, make my life easy".

OTOH my 6th machine runs native ZFS on Linux, and I have to tell that it
shows orders of magnitude better performance and never gave me a single
problem in several (3 ?) years. Only upgrading the distro is always a
big frightening and problematic. And initial installation was a bit tricky.

Probably a lot of BTRS early adopters choosed it for the same reason why
I did : Included in the standard kernel, easy to install, and *expected*
to improve quickly - yes, I already made the move back and forth twice,
between ext4 and BTRFS, on 2 machines... About one year ago I choosed to
jump "for good" and stay, but performance degrades so quickly and so
much that every couple of days I wonder if I won't rollback to ex4 again
(and again), or shift to ZFS once for all and just forget about it...

Everytime I show my Linux machines to friends and say : “Hey, I got the
most advanced filesystem on earth !” I soon get the answer “Oh boy,
that's the slowest machine boot and FS I've ever seen since I was
reading floppy disks on my 386SX in 1991 ! Can you really live with this ?”

So, for "not quite there" and the return codes "+20" that have been a
minor pain in the arse for a couple years but the line is still in the
code... I can understand developer's PoV, been there, done that, but
still, BTRFS might in the end lose a numer of its early adopters if it
keeps being "not quite there" too long.

Shitfing to ZFS is just a PPA and 2 apt-get install commands away... It
will definitely be easier than start playing with mainline PPA Ubuntu
kernels...

Kind regards.

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.


  reply	other threads:[~2013-02-21 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 15:46 Another defrag question Swâmi Petaramesh
2013-02-21 15:50 ` Liu Bo
2013-02-21 15:55   ` Swâmi Petaramesh
2013-02-21 15:54 ` Calvin Walton
2013-02-21 16:01   ` Swâmi Petaramesh
2013-02-21 16:09     ` Blair Zajac
2013-02-21 16:38     ` Hugo Mills
2013-02-21 17:03       ` Swâmi Petaramesh
2013-02-21 17:25         ` Hugo Mills
2013-02-21 17:47           ` Swâmi Petaramesh [this message]
2013-02-21 20:46             ` Hugo Mills
2013-02-21 20:58             ` Bardur Arantsson
2013-02-21 21:56               ` David Sterba
2013-02-22  5:55                 ` Bardur Arantsson
2013-02-21 21:31             ` Johannes Hirte

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=51265DB0.2060407@petaramesh.org \
    --to=swami@petaramesh.org \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@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