From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: wqu@suse.com, dsterba@suse.com,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: [6.2][regression] after commit 947a629988f191807d2d22ba63ae18259bb645c5 btrfs volume periodical forced switch to readonly after a lot of disk writes
Date: Mon, 26 Dec 2022 11:29:42 +0800 [thread overview]
Message-ID: <18b5fa1e-7d1e-4560-c98b-d7ac5fc87c3a@gmx.com> (raw)
In-Reply-To: <CABXGCsNrm3ddn3p_ECSRe+yQeoF3KojTFvy-CpXNzi9ADkbnvQ@mail.gmail.com>
On 2022/12/26 10:47, Mikhail Gavrilov wrote:
> On Mon, Dec 26, 2022 at 5:15 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>> Thanks a lot for the full kernel log.
>>
>> It indeed shows something is wrong in the run_one_delayed_ref().
>> But surprisingly, if there is something wrong, I'd expect more output
>> from btrfs, as normally if one tree block failed to pass whatever the
>> checks, it should cause an error message at least.
>>
>> Since you can reproduce the bug (although I don't think this is easy to
>> reproduce), mind to apply the extra debug patch and then try to reproduce?
>
> Of course I am still able to reproduce.
> The number of messages foreshadowing readonly has become somewhat more:
> [ 2295.155437] BTRFS error (device nvme0n1p3): level check failed on
> logical 4957418700800 mirror 1 wanted 0 found 1
OK, indeed a level mismatch.
From the remaining lines, it shows we're failing at
do_free_extent_accounting(), which failed at the btrfs_del_csums().
And inside btrfs_del_csums(), what we do are all regular btree
operations, thus the tree level check should work without problem.
Thus it seems to be a corrupted csum tree.
> [ 2295.155831] BTRFS error (device nvme0n1p3: state A): Transaction
> aborted (error -5)
> [ 2295.155946] BTRFS: error (device nvme0n1p3: state A) in
> do_free_extent_accounting:2849: errno=-5 IO failure
> [ 2295.155978] BTRFS info (device nvme0n1p3: state EA): forced readonly
> [ 2295.155985] BTRFS error (device nvme0n1p3: state EA):
> run_one_delayed_ref returned -5
> [ 2295.156051] BTRFS: error (device nvme0n1p3: state EA) in
> btrfs_run_delayed_refs:2153: errno=-5 IO failure
>
> Of course full logs are also attached.
>
>> Another thing is, mind to run "btrfs check --readonly" on the fs?
> Result of check attached too.
>
Could you please run "btrfs check --readonly" from a liveCD?
There are tons of possible false alerts if ran on a RW mounted fs.
Thanks,
Qu
next prev parent reply other threads:[~2022-12-26 3:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 21:32 Mikhail Gavrilov
2022-12-26 0:14 ` Qu Wenruo
2022-12-26 2:47 ` Mikhail Gavrilov
2022-12-26 3:29 ` Qu Wenruo [this message]
2022-12-26 7:25 ` David Arendt
2022-12-26 7:31 ` Write time corrupting for log tree Qu Wenruo
2023-01-03 10:41 ` [6.2][regression] after commit 947a629988f191807d2d22ba63ae18259bb645c5 btrfs volume periodical forced switch to readonly after a lot of disk writes Filipe Manana
2022-12-26 8:15 ` Mikhail Gavrilov
2022-12-26 8:47 ` Qu Wenruo
2022-12-26 11:14 ` Mikhail Gavrilov
2022-12-26 12:11 ` Qu Wenruo
2022-12-26 12:15 ` Mikhail Gavrilov
2022-12-26 23:36 ` Qu Wenruo
2022-12-26 23:52 ` Mikhail Gavrilov
2022-12-27 0:18 ` Qu Wenruo
2022-12-27 1:35 ` Mikhail Gavrilov
2022-12-27 5:13 ` Qu Wenruo
2022-12-27 10:19 ` Mikhail Gavrilov
2022-12-27 11:02 ` Qu Wenruo
2022-12-27 13:11 ` Mikhail Gavrilov
2022-12-28 1:08 ` Qu Wenruo
2022-12-28 14:12 ` Mikhail Gavrilov
2022-12-28 23:24 ` Qu Wenruo
2022-12-28 23:42 ` Mikhail Gavrilov
2022-12-29 0:00 ` Qu Wenruo
2022-12-28 23:31 ` Qu Wenruo
2022-12-29 0:08 ` Mikhail Gavrilov
2022-12-29 3:05 ` Qu Wenruo
2022-12-26 13:37 ` [6.2][regression] after commit 947a629988f191807d2d22ba63ae18259bb645c5 btrfs volume periodical forced switch to readonly after a lot of disk writes #forregzbot Thorsten Leemhuis
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=18b5fa1e-7d1e-4560-c98b-d7ac5fc87c3a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=wqu@suse.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
all inboxes | Powered by JetHome®