From: Nikita Ofitserov via B4 Relay <devnull+himikof.gmail.com@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, Nikita Ofitserov <himikof@gmail.com>
Subject: [PATCH v2 00/15] Accounting for accurate progress reporting
Date: Thu, 28 Aug 2025 17:16:02 +0300 [thread overview]
Message-ID: <20250828-better-progress-v2-0-c088a2003940@gmail.com> (raw)
This patch series introduces new per-btree accounting counters and uses
them for (hopefully) accurate progress reporting in recovery passes.
Also includes various assorted bugfixes.
The commit "Relax restrictions on the number of accounting
counters" is optional, but will likely greatly improve the
upgrade/tools version mismatch experience. Without it, all bree usage
accounting will be thrown out and rebuilt on any version mismatch.
The commit "bcachefs_metadata_version_btree_node_accounting"
introduces the format change along with upgrade/downgrade table entries.
The first ten commits are drive-by fixes/improvements, especially
"Improve check_allocations pass speed not in fsck", which should make
future accounting upgrades much faster (including this one).
Signed-off-by: Nikita Ofitserov <himikof@gmail.com>
---
Changes in v2:
- Reordered the format-change-dependent commits to the end
- Added the new metadata version, upgrade and downgrade entries
- Fixed an issue with hidden usage calculation after device removal
- Link to v1: https://lore.kernel.org/r/20250827-better-progress-v1-0-74c24de7988a@gmail.com
---
Nikita Ofitserov (15):
bcachefs: Introduce btree_leaf_has_triggers_mask
bcachefs: Refactor bch2_gc_btree/bch2_gc_btrees
bcachefs: Improve check_allocations pass speed when not in fsck
bcachefs: Refactor/rename btree_type_has_ptrs
bcachefs: Fix progress reporting for unknown btrees
bcachefs: Partially fix old device removal with unknown btrees
bcachefs: Fix missing c->usage updates from early recovery
bcachefs: Optimize/fix bch2_dev_usage_remove
bcachefs: Fix online hidden (sb+journal) data accounting
bcachefs: Fix outdated documentation comment
bcachefs: Relax restrictions on the number of accounting counters
bcachefs: bcachefs_metadata_version_btree_node_accounting
bcachefs: Use explicit node counts in progress reporting
bcachefs: Better progress reporting for btree iteration without leaves
bcachefs: More accurate progress reporting for inner node iteration
fs/bcachefs/alloc_background.c | 2 +-
fs/bcachefs/backpointers.c | 6 ++--
fs/bcachefs/bcachefs_format.h | 4 +--
fs/bcachefs/btree_gc.c | 28 ++++++++++-----
fs/bcachefs/btree_trans_commit.c | 3 ++
fs/bcachefs/btree_types.h | 11 +++---
fs/bcachefs/buckets.c | 16 ++++++---
fs/bcachefs/disk_accounting.c | 70 ++++++++++++++++++++++++++----------
fs/bcachefs/disk_accounting.h | 16 +++++----
fs/bcachefs/disk_accounting_format.h | 10 +++++-
fs/bcachefs/migrate.c | 18 ++++++----
fs/bcachefs/move.c | 2 +-
fs/bcachefs/progress.c | 41 +++++++++++++++++----
fs/bcachefs/progress.h | 12 ++++++-
fs/bcachefs/sb-downgrade.c | 11 ++++--
15 files changed, 184 insertions(+), 66 deletions(-)
---
base-commit: 753b29cc79897dd7f776fa09654196f5b25f8b96
change-id: 20250826-better-progress-835d946a3c38
Best regards,
--
Nikita Ofitserov
next reply other threads:[~2025-08-28 14:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 14:16 Nikita Ofitserov via B4 Relay [this message]
2025-08-28 14:16 ` [PATCH v2 01/15] bcachefs: Introduce btree_leaf_has_triggers_mask Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 02/15] bcachefs: Refactor bch2_gc_btree/bch2_gc_btrees Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 03/15] bcachefs: Improve check_allocations pass speed when not in fsck Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 04/15] bcachefs: Refactor/rename btree_type_has_ptrs Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 05/15] bcachefs: Fix progress reporting for unknown btrees Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 06/15] bcachefs: Partially fix old device removal with " Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 07/15] bcachefs: Fix missing c->usage updates from early recovery Nikita Ofitserov via B4 Relay
2025-09-01 23:55 ` Kent Overstreet
2025-08-28 14:16 ` [PATCH v2 08/15] bcachefs: Optimize/fix bch2_dev_usage_remove Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 09/15] bcachefs: Fix online hidden (sb+journal) data accounting Nikita Ofitserov via B4 Relay
2025-09-02 0:14 ` Kent Overstreet
2025-08-28 14:16 ` [PATCH v2 10/15] bcachefs: Fix outdated documentation comment Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 11/15] bcachefs: Relax restrictions on the number of accounting counters Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 12/15] bcachefs: bcachefs_metadata_version_btree_node_accounting Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 13/15] bcachefs: Use explicit node counts in progress reporting Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 14/15] bcachefs: Better progress reporting for btree iteration without leaves Nikita Ofitserov via B4 Relay
2025-08-28 14:16 ` [PATCH v2 15/15] bcachefs: More accurate progress reporting for inner node iteration Nikita Ofitserov via B4 Relay
2025-09-01 22:33 ` [PATCH v2 00/15] Accounting for accurate progress reporting Kent Overstreet
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=20250828-better-progress-v2-0-c088a2003940@gmail.com \
--to=devnull+himikof.gmail.com@kernel.org \
--cc=himikof@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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