From: Roman Mamedov <rm@romanrm.net>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 4.14 balance: kernel BUG at /home/kernel/COD/linux/fs/btrfs/ctree.c:1856!
Date: Sat, 18 Nov 2017 14:40:37 +0500 [thread overview]
Message-ID: <20171118144037.0fa8ad4b@natsu> (raw)
In-Reply-To: <5000f429-8b4b-b4ea-5e38-89f7c91af6f3@mendix.com>
On Sat, 18 Nov 2017 02:08:46 +0100
Hans van Kranenburg <hans.van.kranenburg@mendix.com> wrote:
> It's using send + balance at the same time. There's something that makes
> btrfs explode when you do that.
>
> It's not new in 4.14, I have seen it in 4.7 and 4.9 also, various
> different explosions in kernel log. Since that happened, I made sure I
> never did those two things at the same time.
Shouldn't it prevent send during balance, or balance during send then, if
that's the case?
You talk about it "exploding" like it's a normal thing, to have Invalid opcode
BUGs in kernel log, and the user has to take care to not use two of the
regular FS features at the same time.
Seems to be a bug which should be fixed, rather than warning everyone "not to
send during balance".
--
With respect,
Roman
next prev parent reply other threads:[~2017-11-18 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 0:49 4.14 balance: kernel BUG at /home/kernel/COD/linux/fs/btrfs/ctree.c:1856! Tomasz Chmielewski
2017-11-18 1:08 ` Hans van Kranenburg
2017-11-18 1:15 ` Tomasz Chmielewski
2017-11-18 9:40 ` Roman Mamedov [this message]
2017-11-18 10:41 ` waxhead
2017-11-18 11:48 ` Hans van Kranenburg
2017-11-18 12:29 ` Hans van Kranenburg
2017-11-18 19:11 ` Hans van Kranenburg
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=20171118144037.0fa8ad4b@natsu \
--to=rm@romanrm.net \
--cc=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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