From: Naohiro Aota <Naohiro.Aota@wdc.com>
To: Johannes Thumshirn <jth@kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Naohiro Aota <Naohiro.Aota@wdc.com>,
David Sterba <dsterba@suse.com>,
Damien Le Moal <dlemoal@kernel.org>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Yuwei Han <hrx@bupt.moe>
Subject: Re: [PATCH] btrfs: zoned: don't fail mount needlessly due to too many active zones
Date: Mon, 22 Sep 2025 08:10:42 +0000 [thread overview]
Message-ID: <DCZ6CIRZP5KL.8U1RYLST6VJ3@wdc.com> (raw)
In-Reply-To: <20250918105119.41556-1-jth@kernel.org>
On Thu Sep 18, 2025 at 7:51 PM JST, Johannes Thumshirn wrote:
> From: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>
> Previously BTRFS did not look at a device's reported max_open_zones limit,
> but starting with commit 04147d8394e8 ("btrfs: zoned: limit active zones
> to max_open_zones"), zoned BTRFS limited the number of concurrently used
> block-groups to the number of max_open_zones a device reported, if it
> hadn't already reported a number of max_active_zones.
>
> Starting with commit 04147d8394e8 the number of open zones is treated the
> same way as active zones. But this leads to mount failures on filesystems
> which have been used before 04147d8394e8 because too many zones are in an
> open state.
>
> Ignore the new limitations on these filesystems, so zones can be finished
> or evacuated.
>
> Reported-by: Yuwei Han <hrx@bupt.moe>
> Fixes: 04147d8394e8 ("btrfs: zoned: limit active zones to max_open_zones")
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Reviewed-by: Naohiro Aota <naohiro.aota@wdc.com>
prev parent reply other threads:[~2025-09-22 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 10:51 [PATCH] btrfs: zoned: don't fail mount needlessly due to too many active zones Johannes Thumshirn
2025-09-22 8:10 ` Naohiro Aota [this message]
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=DCZ6CIRZP5KL.8U1RYLST6VJ3@wdc.com \
--to=naohiro.aota@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=hrx@bupt.moe \
--cc=jth@kernel.org \
--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