From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Bart Noordervliet <bart@noordervliet.net>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS cache problem
Date: Sun, 11 Nov 2012 17:02:13 +0100 [thread overview]
Message-ID: <509FCC05.9050108@petaramesh.org> (raw)
In-Reply-To: <CAGy7Utg1QPk73AxmYSMFc97BN+9yYU0P-wNexvDOhKD6YOR--Q@mail.gmail.com>
Le 11/11/2012 16:13, Bart Noordervliet a écrit :
> May I also suggest that you maybe shouldn't be running an experimental
> filesystem on a laptop that you can't go without?
I might well be retired before BTRFS is no more "experimental", but I
need its features now...
Otherwise I could go with “ZFS on Linux” that has proven fairly
excellent and much faster and more stable than BTRFS on the machine on
which I've been using it for ~2 years...
I chosed to go for BTRFS on this machine because it's officially part of
the Linux kernel and I would expect it to improve (quickly) over time...
But for now I have to admit that I regret my choice performance wise
(which is terrible...) and stability wise (Already 2 reinstalls with
complete format, if there's a next one, the next one will be ZFS...)
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next prev parent reply other threads:[~2012-11-11 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 22:14 BTRFS cache problem Swâmi Petaramesh
2012-11-11 14:05 ` Bart Noordervliet
2012-11-11 14:13 ` Swâmi Petaramesh
[not found] ` <CAGy7UtgrdGpC5uav0m0yX1oJ47OR6WsX0vOtKu4p5umS4hZUtw@mail.gmail.com>
2012-11-11 14:26 ` Swâmi Petaramesh
2012-11-11 15:13 ` Bart Noordervliet
2012-11-11 16:02 ` Swâmi Petaramesh [this message]
2012-11-11 15:20 ` Hugo Mills
2012-11-11 15:28 ` Swâmi Petaramesh
2012-11-11 15:37 ` Hugo Mills
2012-11-11 16:21 ` Swâmi Petaramesh
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=509FCC05.9050108@petaramesh.org \
--to=swami@petaramesh.org \
--cc=bart@noordervliet.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.