From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
Cc: 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 10:15:23 +0900 [thread overview]
Message-ID: <bbe5a5f53efffcd38db8de92f519beca@wpkg.org> (raw)
In-Reply-To: <5000f429-8b4b-b4ea-5e38-89f7c91af6f3@mendix.com>
On 2017-11-18 10:08, Hans van Kranenburg wrote:
> On 11/18/2017 01:49 AM, Tomasz Chmielewski wrote:
>> I'm getting the following BUG when running balance on one of my
>> systems:
>>
>>
>> [ 3458.698704] BTRFS info (device sdb3): relocating block group
>> 306045779968 flags data|raid1
>> [ 3466.892933] BTRFS info (device sdb3): found 2405 extents
>> [ 3495.408630] BTRFS info (device sdb3): found 2405 extents
>> [ 3498.161144] ------------[ cut here ]------------
>> [ 3498.161150] kernel BUG at
>> /home/kernel/COD/linux/fs/btrfs/ctree.c:1856!
>> [ 3498.161264] invalid opcode: 0000 [#1] SMP
(...)
>> [ 3498.164523] Call Trace:
>> [ 3498.164694] tree_advance+0x16e/0x1d0 [btrfs]
>> [ 3498.164874] btrfs_compare_trees+0x2da/0x6a0 [btrfs]
>> [ 3498.165078] ? process_extent+0x1580/0x1580 [btrfs]
>> [ 3498.165264] btrfs_ioctl_send+0xe94/0x1120 [btrfs]
>
> 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.
Indeed, send was started when balance was running.
Thanks for the hint.
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2017-11-18 1:15 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 [this message]
2017-11-18 9:40 ` Roman Mamedov
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=bbe5a5f53efffcd38db8de92f519beca@wpkg.org \
--to=mangoo@wpkg.org \
--cc=hans.van.kranenburg@mendix.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