From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Qu Wenruo <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: Thu, 29 Dec 2022 08:00:11 +0800 [thread overview]
Message-ID: <52793f07-a842-dac0-b7c2-bca641e18a94@gmx.com> (raw)
In-Reply-To: <CABXGCsMhtEFDWYhFU25X3NSw3R3z8byV23F_E0EgSEfcvHrZFw@mail.gmail.com>
On 2022/12/29 07:42, Mikhail Gavrilov wrote:
> On Thu, Dec 29, 2022 at 4:24 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>> Just one last thing to confirm, mind to provide the following dump?
>>
>> # btrfs ins dump-tree -t chunk <device>
>>
>> If the fix works, it means you have some tree block crossing stripe
>> boundary, which is not the ideal situation.
>
> I attached this dump.
> The only thing that I did from a working system I hope it is not
> affected to result?
>
For small dumps like chunk tree, it's completely fine to dump from live
systems.
And your dumps (along with your previous debug output) shows no metadata
crossing stripe boundaries.
I'd need dig deeper why btrfs is splitting extent buffers unnecessarily.
Thanks,
Qu
next prev parent reply other threads:[~2022-12-29 0:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 21:32 [6.2][regression] after commit 947a629988f191807d2d22ba63ae18259bb645c5 btrfs volume periodical forced switch to readonly after a lot of disk writes Mikhail Gavrilov
2022-12-26 0:14 ` Qu Wenruo
2022-12-26 2:47 ` Mikhail Gavrilov
2022-12-26 3:29 ` Qu Wenruo
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 [this message]
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=52793f07-a842-dac0-b7c2-bca641e18a94@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;
as well as URLs for NNTP newsgroup(s).