From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Filipe Manana <fdmanana@kernel.org>,
Andrea Gelmini <andrea.gelmini@gmail.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
dsterba@suse.com, josef@toxicpanda.com, Qu Wenruo <wqu@suse.com>
Subject: Re: 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory
Date: Fri, 5 Jul 2024 08:02:46 +0930 [thread overview]
Message-ID: <0246e506-db8b-47a8-94f0-943e7be92dcc@gmx.com> (raw)
In-Reply-To: <CAL3q7H5AFbSy0JC=u_MAfNR-J_kFQkaG6_pXJimD80tchFXytg@mail.gmail.com>
在 2024/7/5 02:08, Filipe Manana 写道:
> On Thu, Jul 4, 2024 at 12:19 PM Andrea Gelmini <andrea.gelmini@gmail.com> wrote:
>>
>> Il giorno gio 4 lug 2024 alle ore 11:49 Filipe Manana
>> <fdmanana@kernel.org> ha scritto:
>>> I'll try that soon and see if I can reproduce.
>>
>> I'm creating a qcow installation with everything, to replicate this.
>> Sorry, it takes time.
>>
>> By the way, it's just me? (latest git master btrfs-progs)
>> btrfs-image /dev/blah-blah loop.dd
>> works perfectly, but
>> btrfs-image -s /dev/blah-blah loop.dd
>> generate an image impossible to mount:
>> [gio lug 4 11:20:05 2024] BTRFS info (device loop40): first mount of
>> filesystem 496b800d-2f32-46bb-b8d0-03d6f71cf4b2
>> [gio lug 4 11:20:05 2024] BTRFS info (device loop40): using crc32c
>> (crc32c-intel) checksum algorithm
>> [gio lug 4 11:20:05 2024] BTRFS info (device loop40): using free space tree
>> [gio lug 4 11:20:05 2024] BTRFS critical (device loop40): corrupt
>> leaf: root=1 block=40297906176 slot=6 ino=6, name hash mismatch with
>> key,
>
> Sorry I have no idea about that. I don't use btrfs-image myself and I
> don't think I even ever looked at its source code.
> CC'ing Qu who might be interested in that.
That's the nature of "-s" option unfortunately.
Tree-checker has extra sanity checks to ensure the hash matches the name.
I think it's a little overkilled for image dump, would fix it soon.
Thanks,
Qu
>
> I'll reply very soon to the emails about the performance issues that
> correlated to related to the shrinker, there are some interesting
> things to look for.
>
> Thanks.
>
>
>> have 0x00000000365ce506 expect 0x000000008dbfc2d2
>> [gio lug 4 11:20:05 2024] BTRFS error (device loop40): read time tree
>> block corruption detected on logical 40297906176 mirror 1
>> [gio lug 4 11:20:05 2024] BTRFS critical (device loop40): corrupt
>> leaf: root=1 block=40297906176 slot=6 ino=6, name hash mismatch with
>> key,
>> have 0x00000000365ce506 expect 0x000000008dbfc2d2
>> [gio lug 4 11:20:05 2024] BTRFS error (device loop40): read time tree
>> block corruption detected on logical 40297906176 mirror 2
>> [gio lug 4 11:20:05 2024] BTRFS warning (device loop40): couldn't
>> read tree root
>> [gio lug 4 11:20:05 2024] BTRFS error (device loop40): open_ctree failed
>>
>>> In the meanwhile, just curious: are you using swapfiles on btrfs?
>>
>> never used on BTRFS (i have a dedicated nvme partition).
>>
>> Same effect also disabling the swap, btw, and thp.
>
next prev parent reply other threads:[~2024-07-04 22:32 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 20:56 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory Mikhail Gavrilov
2024-06-26 10:48 ` Filipe Manana
2024-06-26 14:16 ` Mikhail Gavrilov
2024-07-01 9:30 ` Filipe Manana
2024-07-02 14:13 ` Mikhail Gavrilov
2024-07-02 17:22 ` Filipe Manana
2024-07-02 19:46 ` Chris Murphy
2024-07-03 10:32 ` Filipe Manana
2024-07-03 10:31 ` Filipe Manana
2024-07-03 10:44 ` Filipe Manana
2024-07-03 21:07 ` Andrea Gelmini
2024-07-04 9:48 ` Filipe Manana
2024-07-04 9:56 ` Filipe Manana
2024-07-04 10:50 ` Mikhail Gavrilov
2024-07-04 13:33 ` Andrea Gelmini
2024-07-04 13:47 ` Andrea Gelmini
2024-07-04 14:48 ` Andrea Gelmini
2024-07-04 17:25 ` Filipe Manana
2024-07-04 17:31 ` Filipe Manana
2024-07-04 22:15 ` Andrea Gelmini
2024-07-04 22:23 ` Andrea Gelmini
2024-07-05 11:00 ` Filipe Manana
2024-07-05 6:30 ` Andrea Gelmini
2024-07-05 11:06 ` Filipe Manana
2024-07-05 18:36 ` Mikhail Gavrilov
2024-07-05 23:09 ` Filipe Manana
2024-07-06 0:11 ` Andrea Gelmini
2024-07-06 12:07 ` Andrea Gelmini
2024-07-06 17:37 ` Filipe Manana
2024-07-07 9:41 ` Filipe Manana
2024-07-07 10:15 ` Andrea Gelmini
2024-07-07 10:28 ` Filipe Manana
2024-07-07 11:15 ` Andrea Gelmini
2024-07-07 12:10 ` Filipe Manana
2024-07-07 11:35 ` Mikhail Gavrilov
2024-07-07 12:15 ` Filipe Manana
2024-07-07 19:16 ` Mikhail Gavrilov
2024-07-08 14:15 ` Filipe Manana
2024-07-10 9:24 ` Mikhail Gavrilov
2024-07-10 10:53 ` Filipe Manana
2024-08-11 8:08 ` Jannik Glückert
2024-08-11 15:33 ` Filipe Manana
2024-08-14 21:24 ` Jannik Glückert
2024-08-15 22:21 ` intelfx
2024-08-15 23:17 ` intelfx
2024-08-16 0:02 ` David Sterba
2024-08-16 6:42 ` Andrea Gelmini
2024-08-16 6:47 ` Ivan Shapovalov
2024-08-16 7:45 ` Qu Wenruo
2024-08-16 10:58 ` Filipe Manana
2024-08-16 11:16 ` Ivan Shapovalov
2024-09-26 13:45 ` Filipe Manana
2024-07-04 11:18 ` Andrea Gelmini
2024-07-04 16:38 ` Filipe Manana
2024-07-04 22:32 ` Qu Wenruo [this message]
2024-07-05 6:18 ` Andrea Gelmini
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=0246e506-db8b-47a8-94f0-943e7be92dcc@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=andrea.gelmini@gmail.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
--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