From: "Naohiro Aota" <Naohiro.Aota@wdc.com>
To: "Dongjiang Zhu" <zhudongjiang@fygo.io>, <linux-btrfs@vger.kernel.org>
Cc: <johannes.thumshirn@wdc.com>, <naohiro.aota@wdc.com>
Subject: Re: [PATCH v3 2/4] btrfs: zoned: recover active non-data block group roles on mount
Date: Fri, 28 Aug 2026 14:43:28 +0900 [thread overview]
Message-ID: <DL0C63K7IW67.257PVUA638Z6E@wdc.com> (raw)
In-Reply-To: <65f5e1ca743e6c224009c4fe639945ee6c851d0c.1787887776.git.zhudongjiang@fygo.io>
On Fri Aug 28, 2026 at 12:51 PM JST, Dongjiang Zhu wrote:
> After a remount, a later write can activate a new metadata or system
> block group without finishing the recovered one. Repeating this across
> remounts consumes additional active-zone slots and reservations, and can
> eventually exhaust all active-zone slots.
>
> Once no slot is available, activation of a metadata or system block group
> fails. During synchronous transaction writeback this propagates as
> -EAGAIN, aborting the transaction and forcing the filesystem read-only.
>
> A remount/fsync/remount reproducer on an HC620 left two partially used
> sequential metadata block groups active while active_meta_bg remained
> NULL:
>
> bg=343865819136 alloc=176095232 cap=268435456
> bg=344402690048 alloc=3260416 cap=268435456
Please show the reproducer.
>
> active_meta_bg and active_system_bg assign active block groups to the
> normal metadata and system write roles. These runtime-only pointers are
> reset to NULL on every mount.
>
> Mount reconstructs partially used sequential block groups in
> zone_active_bgs and adjusts their reservations, but does not recover the
> role assignments.
>
> The write-time pivot can finish the previous block group only when the
> corresponding role pointer is set. If it is NULL, activation proceeds
> without releasing an already active block group of the same role.
True. But, it is set to the written block group if e.g, active_meta_bg
== NULL. Given that metadata is properly written to partially used block
group, isn't it no problem with that? Apparently, this write-time
setting can be considered as the role recovery.
If it is writing into another block group leaving partially used one
intact, then that is an issue on metadata allocation.
>
> Restore the role assignments by selecting one active block group for the
> normal metadata role and one for the system role from zone_active_bgs.
> For each role, keep the block group with the largest writable tail and
> finish the others.
>
> The tree-log block group role is runtime-only and cannot be recovered
> after a remount. Use the selected metadata block group for the normal
> metadata role and leave one metadata reservation for a new tree-log block
> group.
>
> Run the recovery on every mount. ZONE_FINISH preserves existing extents
> but abandons the unused tail, so account that tail as zone unusable
> immediately.
>
> Assisted-by: LLM
> Signed-off-by: Dongjiang Zhu <zhudongjiang@fygo.io>
> ---
> fs/btrfs/disk-io.c | 7 +++-
> fs/btrfs/zoned.c | 97 ++++++++++++++++++++++++++++++++++++++++++----
> fs/btrfs/zoned.h | 7 +++-
> 3 files changed, 101 insertions(+), 10 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index e6bbb0b1b38c..cd1f46ec62f0 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -3713,7 +3713,12 @@ int __cold open_ctree(struct super_block *sb, struct btrfs_fs_devices *fs_device
>
> btrfs_free_zone_cache(fs_info);
>
> - btrfs_check_active_zone_reservation(fs_info);
> + ret = btrfs_restore_active_nondata_bgs(fs_info);
> + if (ret) {
> + btrfs_err(fs_info, "failed to restore active non-data block groups: %pe",
> + ERR_PTR(ret));
> + goto fail_sysfs;
> + }
>
> if (!sb_rdonly(sb) && fs_info->fs_devices->missing_devices &&
> !btrfs_check_rw_degradable(fs_info, NULL)) {
> diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
> index 0d964ada3ad4..ee7d518bec15 100644
> --- a/fs/btrfs/zoned.c
> +++ b/fs/btrfs/zoned.c
> @@ -3056,22 +3056,77 @@ int btrfs_zoned_activate_one_bg(struct btrfs_space_info *space_info, bool do_fin
> return 0;
> }
>
> +static int finish_extra_active_nondata_bgs(struct btrfs_fs_info *fs_info)
> +{
> + struct btrfs_block_group *block_group;
> + struct btrfs_block_group *next;
> + u64 tail_unusable;
> + int ret;
> +
> + list_for_each_entry_safe(block_group, next, &fs_info->zone_active_bgs,
> + active_bg_list) {
> + if (!(block_group->flags &
> + (BTRFS_BLOCK_GROUP_METADATA | BTRFS_BLOCK_GROUP_SYSTEM)))
> + continue;
> +
> + if (block_group == fs_info->active_meta_bg ||
> + block_group == fs_info->active_system_bg)
> + continue;
> +
> + btrfs_get_block_group(block_group);
Why do we need to do this?
> + spin_lock(&block_group->lock);
> + tail_unusable = block_group->zone_capacity - block_group->alloc_offset;
> + spin_unlock(&block_group->lock);
> +
> + ret = do_zone_finish(block_group, true);
> + if (!ret) {
> + struct btrfs_space_info *space_info = block_group->space_info;
> +
> + /* Account for the unused tail abandoned by ZONE_FINISH. */
> + spin_lock(&space_info->lock);
> + spin_lock(&block_group->lock);
> + block_group->zone_unusable += tail_unusable;
> + btrfs_space_info_update_bytes_zone_unusable(space_info,
> + tail_unusable);
> + spin_unlock(&block_group->lock);
> + spin_unlock(&space_info->lock);
> + }
So, basically, do_zone_finish() should have handled this...
> + btrfs_put_block_group(block_group);
> + if (ret)
> + return ret;
> + }
> +
> + return 0;
> +}
> +
> /*
> - * Reserve zones for one metadata block group, one tree-log block group, and one
> - * system block group.
> + * Restore one active block group for normal metadata and system writes.
> + *
> + * The tree-log block group identity is not persisted, so recovered active
> + * metadata block groups cannot be distinguished by their previous role. Keep
> + * one for the normal metadata role and leave one reservation for a new
> + * tree-log block group.
> + *
> + * Older kernels rebuilt zone_active_bgs at mount without recovering the role
> + * assignments, which could result in multiple active metadata or system block
> + * groups. Finish all but the selected block group for each role.
> */
> -void btrfs_check_active_zone_reservation(struct btrfs_fs_info *fs_info)
> +int btrfs_restore_active_nondata_bgs(struct btrfs_fs_info *fs_info)
> {
> struct btrfs_fs_devices *fs_devices = fs_info->fs_devices;
> struct btrfs_block_group *block_group;
> + struct btrfs_block_group *active_meta_bg = NULL;
> + struct btrfs_block_group *active_system_bg = NULL;
> struct btrfs_device *device;
> + u64 active_meta_avail = 0;
> + u64 active_system_avail = 0;
> /* Reserve zones for normal SINGLE metadata and tree-log block group. */
> unsigned int metadata_reserve = 2;
> /* Reserve a zone for SINGLE system block group. */
> unsigned int system_reserve = 1;
>
> if (!test_bit(BTRFS_FS_ACTIVE_ZONE_TRACKING, &fs_info->flags))
> - return;
> + return 0;
>
> /*
> * This function is called from the mount context. So, there is no
> @@ -3093,14 +3148,38 @@ void btrfs_check_active_zone_reservation(struct btrfs_fs_info *fs_info)
> }
> mutex_unlock(&fs_devices->device_list_mutex);
>
> - /* Release reservation for currently active block groups. */
> + /*
> + * Account all active non-data block groups before selecting one for each role.
> + * Finishing the extra block groups releases their reservations again.
> + */
> spin_lock(&fs_info->zone_active_bgs_lock);
> list_for_each_entry(block_group, &fs_info->zone_active_bgs, active_bg_list) {
> struct btrfs_chunk_map *map = block_group->physical_map;
> + struct btrfs_block_group **active_bg;
> + u64 *active_avail;
> + u64 avail;
>
> - if (!(block_group->flags &
> - (BTRFS_BLOCK_GROUP_METADATA | BTRFS_BLOCK_GROUP_SYSTEM)))
> + if (block_group->flags & BTRFS_BLOCK_GROUP_METADATA) {
> + active_bg = &active_meta_bg;
> + active_avail = &active_meta_avail;
> + } else if (block_group->flags & BTRFS_BLOCK_GROUP_SYSTEM) {
> + active_bg = &active_system_bg;
> + active_avail = &active_system_avail;
> + } else {
> continue;
> + }
> +
> + spin_lock(&block_group->lock);
> + avail = block_group->zone_capacity - block_group->alloc_offset;
> + spin_unlock(&block_group->lock);
> +
> + if (!*active_bg || avail > *active_avail) {
> + if (*active_bg)
> + btrfs_put_block_group(*active_bg);
> + *active_bg = block_group;
> + *active_avail = avail;
> + btrfs_get_block_group(*active_bg);
> + }
>
> for (int i = 0; i < map->num_stripes; i++) {
> struct btrfs_device *device = map->stripes[i].dev;
> @@ -3115,7 +3194,11 @@ void btrfs_check_active_zone_reservation(struct btrfs_fs_info *fs_info)
> device->zone_info->reserved_active_zones--;
> }
> }
> + fs_info->active_meta_bg = active_meta_bg;
> + fs_info->active_system_bg = active_system_bg;
> spin_unlock(&fs_info->zone_active_bgs_lock);
> +
> + return finish_extra_active_nondata_bgs(fs_info);
> }
>
> /*
> diff --git a/fs/btrfs/zoned.h b/fs/btrfs/zoned.h
> index 8e21a836f858..934a9368ed15 100644
> --- a/fs/btrfs/zoned.h
> +++ b/fs/btrfs/zoned.h
> @@ -95,7 +95,7 @@ void btrfs_zoned_release_data_reloc_bg(struct btrfs_fs_info *fs_info, u64 logica
> u64 length);
> int btrfs_zone_finish_one_bg(struct btrfs_fs_info *fs_info);
> int btrfs_zoned_activate_one_bg(struct btrfs_space_info *space_info, bool do_finish);
> -void btrfs_check_active_zone_reservation(struct btrfs_fs_info *fs_info);
> +int btrfs_restore_active_nondata_bgs(struct btrfs_fs_info *fs_info);
> int btrfs_reset_unused_block_groups(struct btrfs_space_info *space_info, u64 num_bytes);
> void btrfs_show_zoned_stats(struct btrfs_fs_info *fs_info, struct seq_file *seq);
>
> @@ -279,7 +279,10 @@ static inline int btrfs_zoned_activate_one_bg(struct btrfs_space_info *space_inf
> return 0;
> }
>
> -static inline void btrfs_check_active_zone_reservation(struct btrfs_fs_info *fs_info) { }
> +static inline int btrfs_restore_active_nondata_bgs(struct btrfs_fs_info *fs_info)
> +{
> + return 0;
> +}
>
> static inline int btrfs_reset_unused_block_groups(struct btrfs_space_info *space_info,
> u64 num_bytes)
next prev parent reply other threads:[~2026-08-28 5:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 3:51 [PATCH v3 0/4] btrfs: zoned: fix active-zone accounting and transitions Dongjiang Zhu
2026-08-28 3:51 ` [PATCH v3 1/4] btrfs: zoned: track only sequential zones as active Dongjiang Zhu
2026-08-28 5:26 ` Naohiro Aota
2026-08-28 3:51 ` [PATCH v3 2/4] btrfs: zoned: recover active non-data block group roles on mount Dongjiang Zhu
2026-08-28 5:43 ` Naohiro Aota [this message]
2026-08-28 12:07 ` Dongjiang Zhu
2026-08-28 3:51 ` [PATCH v3 3/4] btrfs: zoned: remove obsolete non-data block group activation helper Dongjiang Zhu
2026-08-28 3:51 ` [PATCH v3 4/4] btrfs: zoned: serialize zone finishing per block group Dongjiang Zhu
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=DL0C63K7IW67.257PVUA638Z6E@wdc.com \
--to=naohiro.aota@wdc.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zhudongjiang@fygo.io \
/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