From: Marc MERLIN <marc@merlins.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 4.13.12: kernel BUG at fs/btrfs/ctree.h:1802!
Date: Thu, 16 Nov 2017 16:12:56 -0800 [thread overview]
Message-ID: <20171117001256.GN10969@merlins.org> (raw)
In-Reply-To: <2b97e49b-74fd-77c1-a340-8254f8999bb1@applied-asynchrony.com>
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.
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 :-/
> > As for 4.14, the serial console code seems broken though, I can't get login or bash
> > to work anymore on them:
> > [ 2786.305004] INFO: task login:5636 blocked for more than 120 seconds.
> > [ 2786.324648] Tainted: G U W 4.14.0-amd64-stkreg-sysrq-20171018 #1
> > [ 2786.347692] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > [ 2786.371742] login D 0 5636 1 0xa0020006
>
> I'm out. :/
Yeah, I didn't expect you to know, or this list even, just warning that 4.14
is not "that great" yet (although that was before the "bcache will corrupt
your stuff", which now makes it "terrible" :( ).
On the plus side, I'm back to 4.13.12 and it hasn't crashed yet, so maybe
4.14 fixed the issue I had (wishful thinking)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2017-11-17 0:12 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 [this message]
2017-11-17 5:41 ` Roman Mamedov
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=20171117001256.GN10969@merlins.org \
--to=marc@merlins.org \
--cc=holger@applied-asynchrony.com \
--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;
as well as URLs for NNTP newsgroup(s).