From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755802AbcIGAzw (ORCPT ); Tue, 6 Sep 2016 20:55:52 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:34181 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221AbcIGAzu (ORCPT ); Tue, 6 Sep 2016 20:55:50 -0400 Date: Tue, 6 Sep 2016 16:55:46 -0800 From: Kent Overstreet To: Harald Dunkel Cc: linux-kernel@vger.kernel.org Subject: Re: bcache vs bcachefs Message-ID: <20160907005546.dw7hxczrbbmnkplc@kmo-pixel> References: <87wpip9x8r.fsf@sylvester.afaics.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87wpip9x8r.fsf@sylvester.afaics.de> User-Agent: NeoMutt/ (1.7.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.