From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/8] btrfs-progs: add support for write-intent bitmaps
Date: Tue, 5 Jul 2022 15:37:39 +0800 [thread overview]
Message-ID: <cover.1657006141.git.wqu@suse.com> (raw)
This patchset introduces the following support for WRITE_INTENT_BITMAP
compat RO flags:
- mkfs support for EXTRA_SUPER_RESERVED and WRITE_INTENT_BITMAP
The extra reservation size is 1MiB, and is hardcoded so far.
Although write-intent bitmaps will only utilize 4KiB of the extra
1MiB.
- dump-supper support for both compat RO flags
- extra fsck warning when the reserved space is not properly respected
- new "btrfs inspect-internal dump-write-intent" command
This is to dump the content of the write-intent bitmap for debug
purpose.
Qu Wenruo (8):
btrfs-progs: introduce a new compat RO flag, EXTRA_SUPER_RESERVED
btrfs-progs: mkfs: add support for extra-super-reserved runtime flag
btrfs-progs: print-tree: remove duplicated definition for compat RO
flags
btrfs-progs: print-tree: support btrfs_super_block::reserved_bytes
btrfs-progs: check: add extra warning for dev extents inside the
reserved range
btrfs-progs: introduce the experimental compat RO flag,
WRITE_INTENT_BITMAP
btrfs-progs: introduce the on-disk format of btrfs write intent
bitmaps
btrfs-progs: cmds/inspect: add the ability to dump write intent
bitmaps
Makefile | 3 +-
check/main.c | 17 +++
check/mode-lowmem.c | 22 ++++
cmds/commands.h | 1 +
cmds/inspect-dump-write-intent.c | 158 +++++++++++++++++++++++++++
cmds/inspect.c | 1 +
common/fsfeatures.c | 19 ++++
common/fsfeatures.h | 2 +
kernel-shared/ctree.h | 40 ++++++-
kernel-shared/disk-io.c | 18 ++++
kernel-shared/print-tree.c | 104 +++++++++++++++++-
kernel-shared/print-tree.h | 1 +
kernel-shared/volumes.c | 4 +
kernel-shared/write-intent.h | 177 +++++++++++++++++++++++++++++++
mkfs/common.c | 25 +++++
mkfs/main.c | 14 +++
16 files changed, 600 insertions(+), 6 deletions(-)
create mode 100644 cmds/inspect-dump-write-intent.c
create mode 100644 kernel-shared/write-intent.h
--
2.36.1
next reply other threads:[~2022-07-05 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 7:37 Qu Wenruo [this message]
2022-07-05 7:37 ` [PATCH 1/8] btrfs-progs: introduce a new compat RO flag, EXTRA_SUPER_RESERVED Qu Wenruo
2022-07-05 7:37 ` [PATCH 2/8] btrfs-progs: mkfs: add support for extra-super-reserved runtime flag Qu Wenruo
2022-07-05 7:37 ` [PATCH 3/8] btrfs-progs: print-tree: remove duplicated definition for compat RO flags Qu Wenruo
2022-07-05 7:37 ` [PATCH 4/8] btrfs-progs: print-tree: support btrfs_super_block::reserved_bytes Qu Wenruo
2022-07-05 7:37 ` [PATCH 5/8] btrfs-progs: check: add extra warning for dev extents inside the reserved range Qu Wenruo
2022-07-05 7:37 ` [PATCH 6/8] btrfs-progs: introduce the experimental compat RO flag, WRITE_INTENT_BITMAP Qu Wenruo
2022-07-05 7:37 ` [PATCH 7/8] btrfs-progs: introduce the on-disk format of btrfs write intent bitmaps Qu Wenruo
2022-07-05 7:37 ` [PATCH 8/8] btrfs-progs: cmds/inspect: add the ability to dump " Qu Wenruo
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.1657006141.git.wqu@suse.com \
--to=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.