From: Mark Harmstone <mark@harmstone.com>
To: linux-btrfs@vger.kernel.org
Cc: Mark Harmstone <mark@harmstone.com>, Boris Burkov <boris@bur.io>
Subject: [PATCH v7 04/16] btrfs: remove remapped block groups from the free-space tree
Date: Mon, 24 Nov 2025 18:52:56 +0000 [thread overview]
Message-ID: <20251124185335.16556-5-mark@harmstone.com> (raw)
In-Reply-To: <20251124185335.16556-1-mark@harmstone.com>
No new allocations can be done from block groups that have the REMAPPED flag
set, so there's no value in their having entries in the free-space tree.
Prevent a search through the free-space tree being scheduled for such a
block group, and prevent any additions to the in-memory free-space tree.
Signed-off-by: Mark Harmstone <mark@harmstone.com>
Reviewed-by: Boris Burkov <boris@bur.io>
---
fs/btrfs/block-group.c | 19 ++++++++++++++++---
fs/btrfs/free-space-cache.c | 3 +++
2 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/block-group.c b/fs/btrfs/block-group.c
index 6e6939d2e902..53c6bbad7df0 100644
--- a/fs/btrfs/block-group.c
+++ b/fs/btrfs/block-group.c
@@ -933,6 +933,13 @@ int btrfs_cache_block_group(struct btrfs_block_group *cache, bool wait)
if (btrfs_is_zoned(fs_info))
return 0;
+ /*
+ * No allocations can be done from remapped block groups, so they have
+ * no entries in the free-space tree.
+ */
+ if (cache->flags & BTRFS_BLOCK_GROUP_REMAPPED)
+ return 0;
+
caching_ctl = kzalloc(sizeof(*caching_ctl), GFP_NOFS);
if (!caching_ctl)
return -ENOMEM;
@@ -1247,10 +1254,16 @@ int btrfs_remove_block_group(struct btrfs_trans_handle *trans,
* deletes the block group item from the extent tree, allowing for
* another task to attempt to create another block group with the same
* item key (and failing with -EEXIST and a transaction abort).
+ *
+ * If the REMAPPED flag has been set the block group's free space
+ * has already been removed, so we can skip the call to
+ * btrfs_remove_block_group_free_space().
*/
- ret = btrfs_remove_block_group_free_space(trans, block_group);
- if (ret)
- goto out;
+ if (!(block_group->flags & BTRFS_BLOCK_GROUP_REMAPPED)) {
+ ret = btrfs_remove_block_group_free_space(trans, block_group);
+ if (ret)
+ goto out;
+ }
ret = remove_block_group_item(trans, path, block_group);
if (ret < 0)
diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index f0f72850fab2..8d4db3d57cf7 100644
--- a/fs/btrfs/free-space-cache.c
+++ b/fs/btrfs/free-space-cache.c
@@ -2756,6 +2756,9 @@ int btrfs_add_free_space(struct btrfs_block_group *block_group,
{
enum btrfs_trim_state trim_state = BTRFS_TRIM_STATE_UNTRIMMED;
+ if (block_group->flags & BTRFS_BLOCK_GROUP_REMAPPED)
+ return 0;
+
if (btrfs_is_zoned(block_group->fs_info))
return __btrfs_add_free_space_zoned(block_group, bytenr, size,
true);
--
2.51.0
next prev parent reply other threads:[~2025-11-24 18:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 18:52 [PATCH v7 00/16] Remap tree Mark Harmstone
2025-11-24 18:52 ` [PATCH v7 01/16] btrfs: add definitions and constants for remap-tree Mark Harmstone
2025-12-19 1:21 ` David Sterba
2025-11-24 18:52 ` [PATCH v7 02/16] btrfs: add REMAP chunk type Mark Harmstone
2025-12-19 1:27 ` David Sterba
2025-11-24 18:52 ` [PATCH v7 03/16] btrfs: allow remapped chunks to have zero stripes Mark Harmstone
2025-11-24 18:52 ` Mark Harmstone [this message]
2025-11-24 18:52 ` [PATCH v7 05/16] btrfs: don't add metadata items for the remap tree to the extent tree Mark Harmstone
2025-11-24 18:52 ` [PATCH v7 06/16] btrfs: add extended version of struct block_group_item Mark Harmstone
2025-11-24 18:52 ` [PATCH v7 07/16] btrfs: allow mounting filesystems with remap-tree incompat flag Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 08/16] btrfs: redirect I/O for remapped block groups Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 09/16] btrfs: handle deletions from remapped block group Mark Harmstone
2025-11-25 15:59 ` Boris Burkov
2025-11-25 16:06 ` Boris Burkov
2025-12-19 1:45 ` David Sterba
2025-11-24 18:53 ` [PATCH v7 10/16] btrfs: handle setting up relocation of block group with remap-tree Mark Harmstone
2025-12-19 1:56 ` David Sterba
2026-01-06 12:20 ` Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 11/16] btrfs: move existing remaps before relocating block group Mark Harmstone
2025-12-19 2:07 ` David Sterba
2026-01-06 18:28 ` Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 12/16] btrfs: replace identity remaps with actual remaps when doing relocations Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 13/16] btrfs: add do_remap param to btrfs_discard_extent() Mark Harmstone
2025-11-24 18:53 ` [PATCH v7 14/16] btrfs: allow balancing remap tree Mark Harmstone
2025-12-19 2:12 ` David Sterba
2025-11-24 18:53 ` [PATCH v7 15/16] btrfs: handle discarding fully-remapped block groups Mark Harmstone
2025-11-25 16:02 ` Boris Burkov
2025-11-24 18:53 ` [PATCH v7 16/16] btrfs: populate fully_remapped_bgs_list on mount Mark Harmstone
2025-11-27 8:37 ` Boris Burkov
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=20251124185335.16556-5-mark@harmstone.com \
--to=mark@harmstone.com \
--cc=boris@bur.io \
--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