From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7797C0044D for ; Mon, 16 Mar 2020 03:34:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B06012051A for ; Mon, 16 Mar 2020 03:34:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=wpkg.org header.i=@wpkg.org header.b="pWPbyLi8" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729456AbgCPDdQ (ORCPT ); Sun, 15 Mar 2020 23:33:16 -0400 Received: from mail.virtall.com ([46.4.129.203]:60804 "EHLO mail.virtall.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729383AbgCPDdQ (ORCPT ); Sun, 15 Mar 2020 23:33:16 -0400 Received: from mail.virtall.com (localhost [127.0.0.1]) by mail.virtall.com (Postfix) with ESMTP id 3E6F84090EEC for ; Mon, 16 Mar 2020 03:33:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wpkg.org; s=default; t=1584329593; bh=nAhJfD9ooDPpETLkGY2643KtnhF42mUhpEIvicsq1Rc=; h=Date:From:To:Subject:In-Reply-To:References; b=pWPbyLi8iJyTX9kBzpA/3Bh6Zv3/du2ir1nOwma2Gaq9mu7M6KGB2jvAPko0g79Gr qk0NHeBmTsPYA0MjGxhhdoEDZeuinHrrQjWF6TMxksTnDerxA8rMdciWgNDRBUbeK1 d+uX8NPs7RWBsPuK97Hi5iYU3iQSrRnmyrX9yEIQCdLTUnOfDceSv2iNK0za7fl/D1 W0pairx4Y2NXqa/fEQ6IDOej7fDHsqzVmdtN7O6X6+E70sSR/TN+3YmkoK++LUg7FI hRMnRZYbHGbz7FVmKkgrqcW5BgVLeXx74b2ckFhg+R4fbyemkg9q5Ap+OTL/yBQKYS 1s1W6bPDIbP+Q== X-Fuglu-Suspect: 4c3ed368d5244df0baf90c574157af70 X-Fuglu-Spamstatus: NO Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: tch@virtall.com) by mail.virtall.com (Postfix) with ESMTPSA for ; Mon, 16 Mar 2020 03:33:05 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 16 Mar 2020 12:33:04 +0900 From: Tomasz Chmielewski To: Btrfs BTRFS Subject: Re: kernel panic after upgrading to Linux 5.5 In-Reply-To: <8374ca28bc970a51b3378a5a92939c01@wpkg.org> References: <8374ca28bc970a51b3378a5a92939c01@wpkg.org> Message-ID: X-Sender: mangoo@wpkg.org Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On 2020-03-16 12:13, Tomasz Chmielewski wrote: > After upgrading to Linux 5.5 (tried 5.5.6, 5.5.9, also 5.6.0-rc5), the > system panics shortly after mounting and starting to use a btrfs > filesystem. Here is a dmesg - please advise how to deal with it. > It has since crashed several times, because of panic=10 parameter > (system boots, runs for a while, crashes, boots again, and so on). Additionally, I also see that btrfs quota was enabled: > [ 129.044896] CPU: 4 PID: 4476 Comm: btrfs-transacti Kdump: loaded > Not tainted 5.6.0-050600rc5-generic #202003082130 > [ 129.044897] Hardware name: GIGABYTE MZ31-AR0-00/MZ31-AR0-00, BIOS > F03e 09/13/2017 > [ 129.044941] RIP: 0010:btrfs_qgroup_account_extents+0x211/0x250 > [btrfs] How is that possible? I always make sure to disable btrfs quotas after creating a filesystem, and it was also the case here: # history|grep quota 4894 btrfs quota disable /data/lxd # <------ long time ago, history at 4894, now history at >11207 11207 history|grep quota The server does not seem to crash with quotas disabled (at least it's up for 30 mins now). Now I've checked a couple of other servers, and on some of them, quota is also enabled (as verified with "btrfs quota rescan /data/lxd", which in not exiting with an error if the quotas are on - is there a better check to see if the quota is on or off?). That's not very encouraging that quota somehow enables itself. Tomasz Chmielewski https://lxadm.com