From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: kernel panic after upgrading to Linux 5.5
Date: Mon, 16 Mar 2020 12:33:04 +0900 [thread overview]
Message-ID: <bf7cfe71f5217f39458540061ec86589@wpkg.org> (raw)
In-Reply-To: <8374ca28bc970a51b3378a5a92939c01@wpkg.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
next prev parent reply other threads:[~2020-03-16 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 3:13 kernel panic after upgrading to Linux 5.5 Tomasz Chmielewski
2020-03-16 3:33 ` Tomasz Chmielewski [this message]
2020-03-16 5:06 ` Qu Wenruo
2020-03-16 5:19 ` Tomasz Chmielewski
2020-03-16 10:26 ` Qu Wenruo
2020-03-16 12:14 ` Tomasz Chmielewski
2020-03-16 12:32 ` Qu Wenruo
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=bf7cfe71f5217f39458540061ec86589@wpkg.org \
--to=mangoo@wpkg.org \
--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).