From: Kent Overstreet <kent.overstreet@gmail.com>
To: Harald Dunkel <harri@afaics.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bcache vs bcachefs
Date: Tue, 6 Sep 2016 16:55:46 -0800 [thread overview]
Message-ID: <20160907005546.dw7hxczrbbmnkplc@kmo-pixel> (raw)
In-Reply-To: <87wpip9x8r.fsf@sylvester.afaics.de>
On Tue, Sep 06, 2016 at 11:46:28AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> I am pretty hesitant replacing the rock-solid ext4 by bcachefs on my servers.
> Meaning no offense, but surely I would prefer to have ext4 with a thin "SSD
> caching layer" over a completely different filesystem, potentially with alot
> of teething troubles.
>
> Question: Is bcache EOL or can I rely on it for the next 5 to 10 years?
bcache is not EOL - it's still receiving bugfixes.
That said though, there's no reason to expect a long teething period with
bcachefs, it's already more reliable than btrfs in single device mode.
next prev parent reply other threads:[~2016-09-07 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 9:46 bcache vs bcachefs Harald Dunkel
2016-09-07 0:55 ` Kent Overstreet [this message]
2016-09-07 14:34 ` Austin S. Hemmelgarn
2016-09-07 15:55 ` Kent Overstreet
2016-09-08 3:01 ` Theodore Ts'o
2016-09-08 4:24 ` Kent Overstreet
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=20160907005546.dw7hxczrbbmnkplc@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=harri@afaics.de \
--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