From: Johannes Thumshirn <jth@kernel.org>
To: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans Holmberg <Hans.Holmberg@wdc.com>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
hch@lst.de, Damien LeMoal <dlemoal@kernel.org>,
Boris Burkov <boris@bur.io>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: [PATCH RFC 0/3] btrfs: zoned: reclaim block-groups more aggressively
Date: Thu, 28 Mar 2024 14:56:30 +0100 [thread overview]
Message-ID: <20240328-hans-v1-0-4cd558959407@kernel.org> (raw)
Recently we had reports internally that zoned btrfs can get to -ENOSPC
prematurely, because we're running out of allocatable zones on the drive.
But we would have enough space left, if we would reclaim more aggressively.
The following fio-job is an example how to trigger the failure.
[test]
filename=$SCRATCH_MNT
readwrite=write
ioengine=libaio
direct=1
loops=2
filesize=$60_PERCENT_OF_DRIVE
bs=128k
The reason this is still an RFC is, it is enough to have DATA block groups
free but not METADATA block groups. Of cause the same principle could be
applied to METADATA block groups as well, but I'd prefer to have a
discussion on the general direction first.
---
Johannes Thumshirn (3):
btrfs: zoned: traverse device list in should reclaim under rcu_read_lock
btrfs: zoned: reserve relocation zone on mount
btrfs: zoned: kick cleaner kthread if low on space
fs/btrfs/disk-io.c | 2 ++
fs/btrfs/zoned.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++--
fs/btrfs/zoned.h | 3 +++
3 files changed, 59 insertions(+), 2 deletions(-)
---
base-commit: c22750cb802ea5fd510fa66f77aefa3a0529951b
change-id: 20240328-hans-2c9e3b4a69e8
Best regards,
--
Johannes Thumshirn <jth@kernel.org>
next reply other threads:[~2024-03-28 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:56 Johannes Thumshirn [this message]
2024-03-28 13:56 ` [PATCH RFC PATCH 1/3] btrfs: zoned: traverse device list in should reclaim under rcu_read_lock Johannes Thumshirn
2024-04-04 19:35 ` David Sterba
2024-03-28 13:56 ` [PATCH RFC PATCH 2/3] btrfs: zoned: reserve relocation zone on mount Johannes Thumshirn
2024-03-28 23:05 ` Damien Le Moal
2024-04-02 6:03 ` Naohiro Aota
2024-04-02 17:04 ` Boris Burkov
2024-04-05 5:03 ` Naohiro Aota
2024-04-05 1:14 ` Naohiro Aota
2024-03-28 13:56 ` [PATCH RFC PATCH 3/3] btrfs: zoned: kick cleaner kthread if low on space Johannes Thumshirn
2024-03-28 23:06 ` Damien Le Moal
2024-04-02 17:09 ` Boris Burkov
2024-04-04 19:45 ` David Sterba
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=20240328-hans-v1-0-4cd558959407@kernel.org \
--to=jth@kernel.org \
--cc=Hans.Holmberg@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dlemoal@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).