btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | btrfs: introduce BTRFS_DEFAULT_RESERVED macrofs/ fs/ fs/ +1 more | +16 | 0 replies | |
| 2/4 | btrfs: warn about dev extents that are inside the reserved rangefs/ | +10 | 0 replies | |
| 3/4 | btrfs: introduce new compat RO flag, EXTRA_SUPER_RESERVEDfs/ fs/ fs/ +3 more | +58 | 0 replies | |
| 4/4 | btrfs: introduce a new experimental compat RO flag, WRITE_INTENT_BITMAPfs/ fs/ fs/ +1 more | +49 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH DRAFT 0/4] btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it
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(-)
Signature · 1 line
2.36.1