From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/3] Fix active zone accounting for zoned
Date: Wed, 1 Mar 2023 16:14:41 -0500 [thread overview]
Message-ID: <cover.1677705092.git.josef@toxicpanda.com> (raw)
Hello,
While trying to get the CI system up and running with the ZNS drives I ran into
this issue where the TEST_DEV would get maxed out on block groups and everything
would start failing with -ENOSPC.
This is because the way we handle active zone tracking isn't correct. We need
to only take into account the used/pinned/zone_unusable counters for the active
block groups, not the system wide counters.
Unfortunately this is kind of annoying in that we have to mirror these counters
for the active block groups. At this point this is the most straightforward way
to fix this. I'm currently running these patches through xfstests, so consider
this as sort of an RFC to make sure the approach seems reasonable. Thanks,
Josef
Josef Bacik (3):
btrfs: rename BTRFS_FS_NO_OVERCOMMIT -> BTRFS_FS_ACTIVE_ZONE_TRACKING
btrfs: clean up space_info usage in btrfs_update_block_group
btrfs: handle active zone accounting properly
fs/btrfs/block-group.c | 51 ++++++++++++++++++-------
fs/btrfs/disk-io.c | 6 +++
fs/btrfs/extent-tree.c | 13 +++++++
fs/btrfs/fs.h | 7 +---
fs/btrfs/space-info.c | 85 +++++++++++++++++++++++++++++++++++++++---
fs/btrfs/space-info.h | 20 +++++++++-
fs/btrfs/zoned.c | 17 ++++++---
7 files changed, 168 insertions(+), 31 deletions(-)
--
2.26.3
next reply other threads:[~2023-03-01 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 21:14 Josef Bacik [this message]
2023-03-01 21:14 ` [PATCH 1/3] btrfs: rename BTRFS_FS_NO_OVERCOMMIT -> BTRFS_FS_ACTIVE_ZONE_TRACKING Josef Bacik
2023-03-02 6:45 ` Anand Jain
2023-03-02 10:03 ` Johannes Thumshirn
2023-03-02 14:45 ` Naohiro Aota
2023-03-01 21:14 ` [PATCH 2/3] btrfs: clean up space_info usage in btrfs_update_block_group Josef Bacik
2023-03-02 6:46 ` Anand Jain
2023-03-02 10:04 ` Johannes Thumshirn
2023-03-02 14:47 ` Naohiro Aota
2023-03-01 21:14 ` [PATCH 3/3] btrfs: handle active zone accounting properly Josef Bacik
2023-03-02 7:01 ` Naohiro Aota
2023-03-02 14:45 ` Naohiro Aota
2023-03-02 16:07 ` Josef Bacik
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=cover.1677705092.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--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