From: David Sterba <dsterba@suse.cz>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v7 06/12] btrfs: clear free space tree on ro->rw remount
Date: Mon, 30 Nov 2020 20:49:41 +0100 [thread overview]
Message-ID: <20201130194941.GI6430@twin.jikos.cz> (raw)
In-Reply-To: <f91ff85f985eeaf8993022453ca21fa4772e28a8.1605736355.git.boris@bur.io>
On Wed, Nov 18, 2020 at 03:06:21PM -0800, Boris Burkov wrote:
> A user might want to revert to v1 or nospace_cache on a root filesystem,
> and much like turning on the free space tree, that can only be done
> remounting from ro->rw. Support clearing the free space tree on such
> mounts by moving it into the shared remount logic.
>
> Since the CLEAR_CACHE option sticks around across remounts, this change
> would result in clearing the tree for ever on every remount, which is
> not desirable. To fix that, add CLEAR_CACHE to the oneshot options we
> clear at mount end, which has the other bonus of not cluttering the
> /proc/mounts output with clear_cache.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
> ---
> fs/btrfs/disk-io.c | 43 ++++++++++++++++++++++---------------------
> 1 file changed, 22 insertions(+), 21 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 0bc7d9766f8c..64e5707f008b 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2892,6 +2892,7 @@ static int btrfs_check_uuid_tree(struct btrfs_fs_info *fs_info)
> void btrfs_clear_oneshot_options(struct btrfs_fs_info *fs_info)
> {
> btrfs_clear_opt(fs_info->mount_opt, USEBACKUPROOT);
> + btrfs_clear_opt(fs_info->mount_opt, CLEAR_CACHE);
> }
>
> /*
> @@ -2901,6 +2902,27 @@ void btrfs_clear_oneshot_options(struct btrfs_fs_info *fs_info)
> int btrfs_mount_rw(struct btrfs_fs_info *fs_info)
> {
> int ret;
> + bool clear_free_space_tree = false;
> +
> + if (btrfs_test_opt(fs_info, CLEAR_CACHE) &&
> + btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE)) {
> + clear_free_space_tree = true;
> + } else if (btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE) &&
> + !btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE_VALID)) {
> + btrfs_warn(fs_info, "free space tree is invalid");
> + clear_free_space_tree = true;
> + }
> +
> + if (clear_free_space_tree) {
> + btrfs_info(fs_info, "clearing free space tree");
> + ret = btrfs_clear_free_space_tree(fs_info);
> + if (ret) {
> + btrfs_warn(fs_info,
> + "failed to clear free space tree: %d", ret);
> + close_ctree(fs_info);
This is probably a copy&paste error, this was originally in open_ctree
that calls close_ctree after errors, but here it's not supposed to be
called.
> + return ret;
> + }
> + }
>
> ret = btrfs_cleanup_fs_roots(fs_info);
> if (ret)
> @@ -2975,7 +2997,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
> struct btrfs_root *chunk_root;
> int ret;
> int err = -EINVAL;
> - int clear_free_space_tree = 0;
> int level;
>
> ret = init_mount_fs_info(fs_info, sb);
> @@ -3377,26 +3398,6 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
> if (sb_rdonly(sb))
> goto clear_oneshot;
>
> - if (btrfs_test_opt(fs_info, CLEAR_CACHE) &&
> - btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE)) {
> - clear_free_space_tree = 1;
> - } else if (btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE) &&
> - !btrfs_fs_compat_ro(fs_info, FREE_SPACE_TREE_VALID)) {
> - btrfs_warn(fs_info, "free space tree is invalid");
> - clear_free_space_tree = 1;
> - }
> -
> - if (clear_free_space_tree) {
> - btrfs_info(fs_info, "clearing free space tree");
> - ret = btrfs_clear_free_space_tree(fs_info);
> - if (ret) {
> - btrfs_warn(fs_info,
> - "failed to clear free space tree: %d", ret);
> - close_ctree(fs_info);
> - return ret;
> - }
> - }
> -
> ret = btrfs_mount_rw(fs_info);
> if (ret) {
> close_ctree(fs_info);
> --
> 2.24.1
next prev parent reply other threads:[~2020-11-30 19:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 23:06 [PATCH v7 00/10] btrfs: free space tree mounting fixes Boris Burkov
2020-11-18 23:06 ` [PATCH v7 01/12] btrfs: lift rw mount setup from mount and remount Boris Burkov
2020-11-23 16:50 ` David Sterba
2020-11-30 23:31 ` Boris Burkov
2020-12-15 18:01 ` David Sterba
2020-11-23 16:57 ` David Sterba
2020-12-01 0:01 ` Boris Burkov
2020-12-15 17:50 ` David Sterba
2020-11-18 23:06 ` [PATCH v7 02/12] btrfs: cleanup all orphan inodes on ro->rw remount Boris Burkov
2020-11-18 23:06 ` [PATCH v7 03/12] btrfs: only mark bg->needs_free_space if free space tree is on Boris Burkov
2020-11-18 23:06 ` [PATCH v7 04/12] btrfs: create free space tree on ro->rw remount Boris Burkov
2020-11-18 23:06 ` [PATCH v7 05/12] btrfs: clear oneshot options on mount and remount Boris Burkov
2020-11-18 23:06 ` [PATCH v7 06/12] btrfs: clear free space tree on ro->rw remount Boris Burkov
2020-11-30 19:49 ` David Sterba [this message]
2020-11-18 23:06 ` [PATCH v7 07/12] btrfs: keep sb cache_generation consistent with space_cache Boris Burkov
2020-11-18 23:06 ` [PATCH v7 08/12] btrfs: use sb state to print space_cache mount option Boris Burkov
2020-11-18 23:06 ` [PATCH v7 09/12] btrfs: warn when remount will not change the free space tree Boris Burkov
2020-11-30 20:05 ` David Sterba
2020-11-18 23:06 ` [PATCH v7 10/12] btrfs: remove free space items when disabling space cache v1 Boris Burkov
2020-11-18 23:06 ` [PATCH v7 11/12] btrfs: skip space_cache v1 setup when not using it Boris Burkov
2020-11-18 23:06 ` [PATCH v7 12/12] btrfs: fix lockdep error creating free space tree Boris Burkov
2020-11-20 21:32 ` [PATCH v7 00/10] btrfs: free space tree mounting fixes David Sterba
2020-11-30 18:24 ` Boris Burkov
2020-11-30 20:29 ` David Sterba
2020-11-30 20:33 ` David Sterba
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=20201130194941.GI6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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