From: Martin Steigerwald <martin@lichtvoll.de>
To: "Stéphane Lesimple" <stephane_btrfs2@lesimple.fr>,
"Qu Wenruo" <wqu@suse.com>, "David Arendt" <admin@prnet.org>,
linux-btrfs@vger.kernel.org, "Qu Wenruo" <quwenruo.btrfs@gmx.com>
Subject: Re: 5.6-5.10 balance regression?
Date: Tue, 29 Dec 2020 10:42:21 +0100 [thread overview]
Message-ID: <11691195.O9o76ZdvQC@merkaba> (raw)
In-Reply-To: <5f819b6c-d737-bb73-5382-370875b599c1@gmx.com>
Qu Wenruo - 29.12.20, 01:44:07 CET:
> So what I can do is only to add a warning message to the problem.
>
> To solve your problem, I also submitted a patch to btrfs-progs, to
> force v1 space cache cleaning even if the fs has v2 space cache
> enabled.
>
> Or, you can disable v2 space cache first, using "btrfs check
> --clear-space-cache v2" first, then "btrfs check --clear-space_cache
> v1", and finally mount the fs with "space_cache=v2" again.
>
> To verify there is no space cache v1 left, you can run the following
> command to verify:
>
> # btrfs ins dump-tree -t root <device> | grep EXTENT_DATA
>
> It should output nothing.
I have v1 space_cache stuff on filesystems which use v2 space_cache as
well, so…
the fully working way to completely switch to spacecache_v2 for any
BTRFS filesystem with space cache v1, is what you wrote above?
Or would it be more straight forward than that with a newer kernel?
Best,
--
Martin
next prev parent reply other threads:[~2020-12-29 9: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
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:42 ` Martin Steigerwald [this message]
2020-12-29 9:31 ` Stéphane Lesimple
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=11691195.O9o76ZdvQC@merkaba \
--to=martin@lichtvoll.de \
--cc=admin@prnet.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stephane_btrfs2@lesimple.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.