From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: kernel panic after upgrading to Linux 5.5
Date: Mon, 16 Mar 2020 14:19:59 +0900 [thread overview]
Message-ID: <553b4596301e2e7bfa05476065c195d0@wpkg.org> (raw)
In-Reply-To: <fa4d1bf5-b800-edba-1fce-ae7108ae023b@gmx.com>
On 2020-03-16 14:06, Qu Wenruo wrote:
> On 2020/3/16 上午11: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).
>>
>> Mount options:
>>
>> noatime,ssd,space_cache=v2,user_subvol_rm_allowed
>>
>>
>>
>> [ 65.777428] BTRFS info (device sda2): enabling ssd optimizations
>> [ 65.777435] BTRFS info (device sda2): using free space tree
>> [ 65.777436] BTRFS info (device sda2): has skinny extents
>> [ 98.225099] BTRFS error (device sda2): parent transid verify failed
>> on 19718118866944 wanted 664218442 found 674530371
>> [ 98.225594] BTRFS error (device sda2): parent transid verify failed
>> on 19718118866944 wanted 664218442 found 674530371
>
> This is the root cause, not quota.
>
> The metadata is already corrupted, and quota is the first to complain
> about it.
Still, should it crash the server, putting it into a cycle of
crash-boot-crash-boot, possibly breaking the filesystem even more?
Also, how do I fix that corruption?
This server had a drive added, a full balance (to RAID-10 for data and
metadata) and scrub a few weeks ago, with no errors. Running scrub now
to see if it shows up anything.
btrfs filesystem stats also shows no errors:
# btrfs device stats /data/lxd
[/dev/sda2].write_io_errs 0
[/dev/sda2].read_io_errs 0
[/dev/sda2].flush_io_errs 0
[/dev/sda2].corruption_errs 0
[/dev/sda2].generation_errs 0
[/dev/sdd2].write_io_errs 0
[/dev/sdd2].read_io_errs 0
[/dev/sdd2].flush_io_errs 0
[/dev/sdd2].corruption_errs 0
[/dev/sdd2].generation_errs 0
[/dev/sdc2].write_io_errs 0
[/dev/sdc2].read_io_errs 0
[/dev/sdc2].flush_io_errs 0
[/dev/sdc2].corruption_errs 0
[/dev/sdc2].generation_errs 0
[/dev/sdb2].write_io_errs 0
[/dev/sdb2].read_io_errs 0
[/dev/sdb2].flush_io_errs 0
[/dev/sdb2].corruption_errs 0
[/dev/sdb2].generation_errs 0
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2020-03-16 5:20 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
2020-03-16 5:06 ` Qu Wenruo
2020-03-16 5:19 ` Tomasz Chmielewski [this message]
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=553b4596301e2e7bfa05476065c195d0@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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).