From: "Stéphane Lesimple" <stephane_btrfs2@lesimple.fr>
To: "Qu Wenruo" <wqu@suse.com>, "David Arendt" <admin@prnet.org>,
"Qu Wenruo" <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: 5.6-5.10 balance regression?
Date: Mon, 28 Dec 2020 17:43:20 +0000 [thread overview]
Message-ID: <518c15d55c3d540b26341a773ff7d99f@lesimple.fr> (raw)
In-Reply-To: <da42984a-1f75-153a-b7fd-145e0d66b6d4@suse.com>
>> unfortunately the problem is no longer reproducible, probably due to
>> writes happening in meantime. If you still want a btrfs-image, I can
>> create one (unfortunately only without data as there is confidential
>> data in it), but as the problem is currently no longer reproducible, I
>> think it probably won't help.
>
> That's fine, at least you get your fs back to normal.
>
> I tried several small balance locally, not reproduced, thus I guess it
> may be related to certain tree layout.
>
> Anyway, I'll wait for another small enough and reproducible report.
This is still reproducible on my FS, and I have the btrfs-image.
I can easily upload it somewhere, but of course I understand downloading
an image of 51G can be impractical.
An other way might be: as I know which block group is causing the problem,
as per the dmesg, maybe I can dump only the part of the metadata relevant
to this block group?
In any case I can run commands on this system, compile a custom btrfs-progs
or a custom kernel with whatever you want me to try, and reboot as many times
as necessary (this is not a production server).
I know it fails in relocate_block_group(), which returns -2, I'm currently
adding a couple printk's here and there to try to pinpoint that better.
Regards,
Stéphane.
next prev parent reply other threads:[~2020-12-28 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 12:11 5.6-5.10 balance regression? Stéphane Lesimple
2020-12-27 13:11 ` David Arendt
2020-12-28 0:06 ` Qu Wenruo
2020-12-28 7:38 ` David Arendt
2020-12-28 7:48 ` Qu Wenruo
2020-12-28 17:43 ` Stéphane Lesimple [this message]
2020-12-28 19:58 ` Stéphane Lesimple
2020-12-28 23:39 ` Qu Wenruo
2020-12-29 0:44 ` Qu Wenruo
2020-12-29 0:59 ` David Arendt
2020-12-29 4:36 ` Qu Wenruo
2020-12-29 9:31 ` Stéphane Lesimple
2020-12-29 9:42 ` Martin Steigerwald
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=518c15d55c3d540b26341a773ff7d99f@lesimple.fr \
--to=stephane_btrfs2@lesimple.fr \
--cc=admin@prnet.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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