From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from len.romanrm.net ([91.121.75.85]:57218 "EHLO len.romanrm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756456AbdKRJkj (ORCPT ); Sat, 18 Nov 2017 04:40:39 -0500 Date: Sat, 18 Nov 2017 14:40:37 +0500 From: Roman Mamedov To: Hans van Kranenburg Cc: Tomasz Chmielewski , Btrfs BTRFS Subject: Re: 4.14 balance: kernel BUG at /home/kernel/COD/linux/fs/btrfs/ctree.c:1856! Message-ID: <20171118144037.0fa8ad4b@natsu> In-Reply-To: <5000f429-8b4b-b4ea-5e38-89f7c91af6f3@mendix.com> References: <5000f429-8b4b-b4ea-5e38-89f7c91af6f3@mendix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sat, 18 Nov 2017 02:08:46 +0100 Hans van Kranenburg 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