From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] btrfs: zoned: do not remove unwritten non-data block group
Date: Fri, 11 Jul 2025 08:10:19 +0000 [thread overview]
Message-ID: <c3ef0c00-81fe-4d6a-8388-90dcecf58f64@wdc.com> (raw)
In-Reply-To: <5fd0a65f2192fc73069f00804317e68cdb6d06d9.1752217584.git.naohiro.aota@wdc.com>
On 11.07.25 09:12, Naohiro Aota wrote:
> There are some reports of "unable to find chunk map for logical 2147483648
> length 16384" error message appears in the dmesg. This means some IOs are
s/the// ~^
> occurring after a block group is removed.
>
> When a metadata tree node is cleaned on the zoned setup, we keep that node
s/the/a ~^
> still dirty and write it out not to create a write hole. However, this can
> make a block group's used bytes == 0 while there is dirty region left.
a dirty region ~^
>
> Such unused block group is moved into the unused_bg list and processed for
Such an unused
> the removal. When the removal succeeds, the block group is removed from the
^~ s/the//
> transaction->dirty_bgs list, so the unused dirty nodes in the block group
> are not sent at the transaction commit time. It will be written at some
> later time e.g, sync or umount, and causes the "unable to find chunk map"
s/the// ~^
> errors.
>
> This can happen relatively easier on SMR whose zone size is 256MB. However,
s/easier/easy/
> calling do_zone_finish() on such block group returns -EAGAIN and keep that
> block group intact, which is why the issue is hidden until now.
>
> Fixes: afba2bc036b0 ("btrfs: zoned: implement active zone tracking")
> CC: stable@vger.kernel.org # 6.1+
> Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Sorry for not spotting these in v1. But I think they can be fixed up
when applying.
Otherwise looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
next prev parent reply other threads:[~2025-07-11 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 7:11 [PATCH v2 0/2] btrfs: zoned: fix removing of unwritten non-data block group Naohiro Aota
2025-07-11 7:11 ` [PATCH v2 1/2] btrfs: zoned: do not remove " Naohiro Aota
2025-07-11 8:10 ` Johannes Thumshirn [this message]
2025-07-11 7:11 ` [PATCH v2 2/2] btrfs: zoned: requeue to unused block group list if zone finish failed Naohiro Aota
2025-07-11 8:12 ` Johannes Thumshirn
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=c3ef0c00-81fe-4d6a-8388-90dcecf58f64@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.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