From: Roman Mamedov <rm@romanrm.net>
To: Marc MERLIN <marc@merlins.org>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
linux-btrfs@vger.kernel.org
Subject: Re: 4.13.12: kernel BUG at fs/btrfs/ctree.h:1802!
Date: Fri, 17 Nov 2017 10:41:48 +0500 [thread overview]
Message-ID: <20171117104148.04986eee@natsu> (raw)
In-Reply-To: <20171117001256.GN10969@merlins.org>
On Thu, 16 Nov 2017 16:12:56 -0800
Marc MERLIN <marc@merlins.org> wrote:
> On Thu, Nov 16, 2017 at 11:32:33PM +0100, Holger Hoffstätte wrote:
> > Don't pop the champagne just yet, I just read that apprently 4.14 broke
> > bcache for some people [1]. Not sure how much that affects you, but it might
> > well make things worse. Yeah, I know, wonderful.
>
> Oh my, that's actually pretty terrible.
> I've just reverted both my machines to 3.13, the last thing I need is more
> btrfs corruption.
Why so far back though, the latest 4.4 and 4.9 are both good series and run
without issues for me since a long time. Or perhaps you meant 4.13 :)
> I'm also starting to question if I should just drop bcache. It does help
> access to a big and slow-ish array, but corruption and periodic btrfs
> full rebuilds is not something I can afford to do timewise :-/
I suggest that you try lvmcache instead. It's much more flexible than bcache,
does pretty much the same job, and has much less of the "hacky" feel to it.
--
With respect,
Roman
next prev parent reply other threads:[~2017-11-17 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 17:04 kernel BUG at fs/btrfs/ctree.h:1802! Marc MERLIN
2017-11-16 17:07 ` 4.13.12: " Marc MERLIN
2017-11-16 17:27 ` Holger Hoffstätte
2017-11-16 21:45 ` Marc MERLIN
2017-11-16 22:32 ` Holger Hoffstätte
2017-11-17 0:12 ` Marc MERLIN
2017-11-17 5:41 ` Roman Mamedov [this message]
2017-11-17 5:53 ` Marc MERLIN
2017-11-17 17:48 ` Marc MERLIN
2017-11-17 19:03 ` Holger Hoffstätte
2017-11-17 1:33 ` Liu Bo
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=20171117104148.04986eee@natsu \
--to=rm@romanrm.net \
--cc=holger@applied-asynchrony.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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;
as well as URLs for NNTP newsgroup(s).