From: Naohiro Aota <naota@elisp.net>
To: linux-btrfs@vger.kernel.org
Cc: Naohiro Aota <naohiro.aota@wdc.com>
Subject: [PATCH 0/4] btrfs: fixes for reclaim
Date: Tue, 6 Jun 2023 14:36:32 +0900 [thread overview]
Message-ID: <cover.1686028197.git.naohiro.aota@wdc.com> (raw)
There are several issues on the reclaim process out there:
- Long-running reclaim process blocks removing unused BGs
- Belonging to the reclaim list blocks it goes to the unused list
- It tries relocation even when FS is read-only
- Temporal failure keep a block group un-reclaimed
This series fixes them.
Naohiro Aota (4):
btrfs: delete unused BGs while reclaiming BGs
btrfs: move out now unused BG from the reclaim list
btrfs: bail out reclaim process if filesystem is read-only
btrfs: reinsert BGs failed to reclaim
fs/btrfs/block-group.c | 43 ++++++++++++++++++++++++++++++++++++++----
1 file changed, 39 insertions(+), 4 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-06 5:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 5:36 Naohiro Aota [this message]
2023-06-06 5:36 ` [PATCH 1/4] btrfs: delete unused BGs while reclaiming BGs Naohiro Aota
2023-06-06 9:54 ` Filipe Manana
2023-06-06 11:32 ` Johannes Thumshirn
2023-06-07 18:48 ` Boris Burkov
2023-06-12 12:50 ` Naohiro Aota
2023-06-06 5:36 ` [PATCH 2/4] btrfs: move out now unused BG from the reclaim list Naohiro Aota
2023-06-06 10:06 ` Filipe Manana
2023-06-06 11:33 ` Johannes Thumshirn
2023-06-06 5:36 ` [PATCH 3/4] btrfs: bail out reclaim process if filesystem is read-only Naohiro Aota
2023-06-06 10:16 ` Filipe Manana
2023-06-06 11:34 ` Johannes Thumshirn
2023-06-06 5:36 ` [PATCH 4/4] btrfs: reinsert BGs failed to reclaim Naohiro Aota
2023-06-06 10:25 ` Filipe Manana
2023-06-06 16:23 ` David Sterba
2023-06-06 23:55 ` Naohiro Aota
2023-06-08 11:48 ` David Sterba
2023-06-08 11:50 ` [PATCH 0/4] btrfs: fixes for reclaim 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=cover.1686028197.git.naohiro.aota@wdc.com \
--to=naota@elisp.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.com \
/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 NNTP newsgroup(s).