From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH DRAFT 0/4] btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it
Date: Wed, 15 Jun 2022 06:50:10 +0800 [thread overview]
Message-ID: <cover.1655246405.git.wqu@suse.com> (raw)
This series of patches will mainly introduce two new compat RO flags:
- EXTRA_SUPER_RESERVED
This will add a new btrfs_super_block member, reserved_bytes, to tell
btrfs exactly how many bytes are reserved at the beginning of each
device.
By default, with this compat RO specified, mkfs.btrfs will reserved
2MiB instead of the original 1MiB.
So that extra 1MiB can be used by other features.
In theory, EXTRA_SUPER_RESERVED doesn't require any extra space to be
reserved, thus we can even keep the old 1MiB reservation but just make
it explicit in the super block.
- WRITE_INTENT_BITMAP
Currently it's still just a place holder.
It will utilize the extra 1MiB space as a per-device write-intent
bitmap.
The idea will be the same as md-bitmap, but only for RAID56
profiles for now.
At mount time, even for RO mount, we will do a mandatory scrub for the
ranges involved in the bitmap, to close the RAID56 write-hole.
If this compat RO is set while not enough reserved space or without
EXTRA_SUPER_RESERVED compat RO, we may want to reject the mount and
provide a way to mount without write intent bitmap.
But that would be implemented when the feature is really implemented.
The first 2 patches patches are just cleanup and add extra warning when
the existing 1MiB reservation is not properly respected.
More heavy-lifting work will be done in btrfs-progs.
Qu Wenruo (4):
btrfs: introduce BTRFS_DEFAULT_RESERVED macro
btrfs: warn about dev extents that are inside the reserved range
btrfs: introduce new compat RO flag, EXTRA_SUPER_RESERVED
btrfs: introduce a new experimental compat RO flag,
WRITE_INTENT_BITMAP
fs/btrfs/ctree.h | 30 +++++++++++++++++++++++---
fs/btrfs/disk-io.c | 29 +++++++++++++++++++++++++
fs/btrfs/extent-tree.c | 6 +++---
fs/btrfs/super.c | 10 ++++-----
fs/btrfs/sysfs.c | 2 ++
fs/btrfs/volumes.c | 43 ++++++++++++++++++++++++++++++++------
fs/btrfs/zoned.c | 8 +++++++
include/uapi/linux/btrfs.h | 17 +++++++++++++++
8 files changed, 128 insertions(+), 17 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-14 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 22:50 Qu Wenruo [this message]
2022-06-14 22:50 ` [PATCH DRAFT 1/4] btrfs: introduce BTRFS_DEFAULT_RESERVED macro Qu Wenruo
2022-06-14 22:50 ` [PATCH DRAFT 2/4] btrfs: warn about dev extents that are inside the reserved range Qu Wenruo
2022-06-14 22:50 ` [PATCH DRAFT 3/4] btrfs: introduce new compat RO flag, EXTRA_SUPER_RESERVED Qu Wenruo
2022-06-14 22:50 ` [PATCH DRAFT 4/4] btrfs: introduce a new experimental compat RO flag, WRITE_INTENT_BITMAP 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.1655246405.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 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).