* [PATCH DRAFT 1/4] btrfs: introduce BTRFS_DEFAULT_RESERVED macro
2022-06-14 22:50 [PATCH DRAFT 0/4] btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it Qu Wenruo
@ 2022-06-14 22:50 ` Qu Wenruo
2022-06-14 22:50 ` [PATCH DRAFT 2/4] btrfs: warn about dev extents that are inside the reserved range Qu Wenruo
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Qu Wenruo @ 2022-06-14 22:50 UTC (permalink / raw)
To: linux-btrfs
Since btrfs-progs v4.1, mkfs.btrfs will reserve the first 1MiB for the
primary super block (at offset 64KiB) and other legacy bootloaders which
may want to store their data there.
Kernel is doing the same behavior around the same time.
However in kernel we just use SZ_1M to express the reserved space, normally
with extra comments when using above SZ_1M.
Here we introduce a new macro, BTRFS_DEFAULT_RESERVED to replace such
SZ_1M usage.
This will make later enlarged per-dev reservation easier to implement.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
fs/btrfs/ctree.h | 7 +++++++
fs/btrfs/extent-tree.c | 6 +++---
fs/btrfs/super.c | 10 +++++-----
fs/btrfs/volumes.c | 7 +------
4 files changed, 16 insertions(+), 14 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index f7afdfd0bae7..62028e7d5799 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -229,6 +229,13 @@ struct btrfs_root_backup {
#define BTRFS_SUPER_INFO_OFFSET SZ_64K
#define BTRFS_SUPER_INFO_SIZE 4096
+/*
+ * The default reserved space for each device.
+ * This range covers the primary superblock, and some other legacy programs like
+ * older bootloader may want to store their data there.
+ */
+#define BTRFS_DEFAULT_RESERVED (SZ_1M)
+
/*
* the super block basically lists the main trees of the FS
* it currently lacks any block count etc etc
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index 8e9f0a99b292..e384dd483eaa 100644
--- a/fs/btrfs/extent-tree.c
+++ b/fs/btrfs/extent-tree.c
@@ -5976,7 +5976,7 @@ int btrfs_error_unpin_extent_range(struct btrfs_fs_info *fs_info,
*/
static int btrfs_trim_free_extents(struct btrfs_device *device, u64 *trimmed)
{
- u64 start = SZ_1M, len = 0, end = 0;
+ u64 start = BTRFS_DEFAULT_RESERVED, len = 0, end = 0;
int ret;
*trimmed = 0;
@@ -6020,8 +6020,8 @@ static int btrfs_trim_free_extents(struct btrfs_device *device, u64 *trimmed)
break;
}
- /* Ensure we skip the reserved area in the first 1M */
- start = max_t(u64, start, SZ_1M);
+ /* Ensure we skip the reserved area of each device. */
+ start = max_t(u64, start, BTRFS_DEFAULT_RESERVED);
/*
* If find_first_clear_extent_bit find a range that spans the
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 719dda57dc7a..c2d051e887be 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -2273,16 +2273,16 @@ static inline int btrfs_calc_avail_data_space(struct btrfs_fs_info *fs_info,
/*
* In order to avoid overwriting the superblock on the drive,
- * btrfs starts at an offset of at least 1MB when doing chunk
- * allocation.
+ * btrfs has some reserved space at the beginning of each
+ * device.
*
* This ensures we have at least min_stripe_size free space
- * after excluding 1MB.
+ * after excluding that reserved space.
*/
- if (avail_space <= SZ_1M + min_stripe_size)
+ if (avail_space <= BTRFS_DEFAULT_RESERVED + min_stripe_size)
continue;
- avail_space -= SZ_1M;
+ avail_space -= BTRFS_DEFAULT_RESERVED;
devices_info[i].dev = device;
devices_info[i].max_avail = avail_space;
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 12a6150ee19d..051d124679d1 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -1396,12 +1396,7 @@ static u64 dev_extent_search_start(struct btrfs_device *device, u64 start)
{
switch (device->fs_devices->chunk_alloc_policy) {
case BTRFS_CHUNK_ALLOC_REGULAR:
- /*
- * We don't want to overwrite the superblock on the drive nor
- * any area used by the boot loader (grub for example), so we
- * make sure to start at an offset of at least 1MB.
- */
- return max_t(u64, start, SZ_1M);
+ return max_t(u64, start, BTRFS_DEFAULT_RESERVED);
case BTRFS_CHUNK_ALLOC_ZONED:
/*
* We don't care about the starting region like regular
--
2.36.1
^ permalink raw reply related [flat|nested] 5+ messages in thread* [PATCH DRAFT 3/4] btrfs: introduce new compat RO flag, EXTRA_SUPER_RESERVED
2022-06-14 22:50 [PATCH DRAFT 0/4] btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it Qu Wenruo
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 ` Qu Wenruo
2022-06-14 22:50 ` [PATCH DRAFT 4/4] btrfs: introduce a new experimental compat RO flag, WRITE_INTENT_BITMAP Qu Wenruo
3 siblings, 0 replies; 5+ messages in thread
From: Qu Wenruo @ 2022-06-14 22:50 UTC (permalink / raw)
To: linux-btrfs
From the beginning of btrfs kernel module, kernel will avoid allocating
dev extents into the first 1MiB of each device, not only for the
superblock at 64KiB, but also for legacy bootloaders to store their
data.
Here for later expansion, we introduce a new compat RO flag,
EXTRA_SUPER_RESERVED, this allows btrfs to have extra reserved space
beyond the default 1MiB.
The extra reserved space can be utilized by things like write-intent
log.
Several new checks are introduced:
- No super_reserved_bytes should be smaller than the old 1MiB limit
- No zoned device support
Such reserved space will be utilized in a no COW way, thus it can
not be supported by zoned device.
We still allow dev extents to exist in the new reserved_bytes range,
this is to allow btrfstune to set reserved_bytes, then rely on kernel
balance to reserve the new space.
But later, if there is any feature relying on the reserved_bytes, we
will disable those features automatically.
There is a special catch, the new member @reserved_bytes is located at
the end of the superblock, to utilize the padding bytes.
The reason is, due to some undetermined extent tree v2 on-disk format
mess, we don't have reliable location inside the reserved8[] array.
I just want a stable location undisturbed.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
fs/btrfs/ctree.h | 14 +++++++++++---
fs/btrfs/disk-io.c | 9 +++++++++
fs/btrfs/sysfs.c | 2 ++
fs/btrfs/volumes.c | 22 ++++++++++++++++++----
fs/btrfs/zoned.c | 8 ++++++++
include/uapi/linux/btrfs.h | 10 ++++++++++
6 files changed, 58 insertions(+), 7 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 62028e7d5799..d29d25339c3e 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -293,14 +293,19 @@ struct btrfs_super_block {
__le64 block_group_root_generation;
u8 block_group_root_level;
- /* future expansion */
u8 reserved8[7];
__le64 reserved[25];
u8 sys_chunk_array[BTRFS_SYSTEM_CHUNK_ARRAY_SIZE];
struct btrfs_root_backup super_roots[BTRFS_NUM_BACKUP_ROOTS];
+ /*
+ * How many bytes are reserved at the beginning of a device.
+ * Should be >= BTRFS_DEFAULT_RESERVED.
+ */
+ __le32 reserved_bytes;
+
/* Padded to 4096 bytes */
- u8 padding[565];
+ u8 padding[561];
} __attribute__ ((__packed__));
static_assert(sizeof(struct btrfs_super_block) == BTRFS_SUPER_INFO_SIZE);
@@ -315,7 +320,8 @@ static_assert(sizeof(struct btrfs_super_block) == BTRFS_SUPER_INFO_SIZE);
#define BTRFS_FEATURE_COMPAT_RO_SUPP \
(BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE | \
BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE_VALID | \
- BTRFS_FEATURE_COMPAT_RO_VERITY)
+ BTRFS_FEATURE_COMPAT_RO_VERITY | \
+ BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED)
#define BTRFS_FEATURE_COMPAT_RO_SAFE_SET 0ULL
#define BTRFS_FEATURE_COMPAT_RO_SAFE_CLEAR 0ULL
@@ -2524,6 +2530,8 @@ BTRFS_SETGET_STACK_FUNCS(super_block_group_root_generation,
block_group_root_generation, 64);
BTRFS_SETGET_STACK_FUNCS(super_block_group_root_level, struct btrfs_super_block,
block_group_root_level, 8);
+BTRFS_SETGET_STACK_FUNCS(super_reserved_bytes, struct btrfs_super_block,
+ reserved_bytes, 32);
int btrfs_super_csum_size(const struct btrfs_super_block *s);
const char *btrfs_super_csum_name(u16 csum_type);
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 800ad3a9c68e..b2184fcdfde9 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -2817,6 +2817,15 @@ static int validate_super(struct btrfs_fs_info *fs_info,
ret = -EINVAL;
}
+ if (btrfs_super_compat_ro_flags(sb) &
+ BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED &&
+ btrfs_super_reserved_bytes(sb) < BTRFS_DEFAULT_RESERVED) {
+ btrfs_err(fs_info,
+"EXTRA_SUPER_RESERVED feature enabled, but reserved space is smaller than default (%u)",
+ BTRFS_DEFAULT_RESERVED);
+ ret = -EINVAL;
+ }
+
/*
* The generation is a global counter, we'll trust it more than the others
* but it's still possible that it's the one that's wrong.
diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
index 3554c7b4204f..e2f5c62f6106 100644
--- a/fs/btrfs/sysfs.c
+++ b/fs/btrfs/sysfs.c
@@ -289,6 +289,7 @@ BTRFS_FEAT_ATTR_INCOMPAT(no_holes, NO_HOLES);
BTRFS_FEAT_ATTR_INCOMPAT(metadata_uuid, METADATA_UUID);
BTRFS_FEAT_ATTR_COMPAT_RO(free_space_tree, FREE_SPACE_TREE);
BTRFS_FEAT_ATTR_INCOMPAT(raid1c34, RAID1C34);
+BTRFS_FEAT_ATTR_COMPAT_RO(extra_super_reserved, EXTRA_SUPER_RESERVED);
#ifdef CONFIG_BLK_DEV_ZONED
BTRFS_FEAT_ATTR_INCOMPAT(zoned, ZONED);
#endif
@@ -321,6 +322,7 @@ static struct attribute *btrfs_supported_feature_attrs[] = {
BTRFS_FEAT_ATTR_PTR(metadata_uuid),
BTRFS_FEAT_ATTR_PTR(free_space_tree),
BTRFS_FEAT_ATTR_PTR(raid1c34),
+ BTRFS_FEAT_ATTR_PTR(extra_super_reserved),
#ifdef CONFIG_BLK_DEV_ZONED
BTRFS_FEAT_ATTR_PTR(zoned),
#endif
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index b39f4030d2ba..5c337d7ef3c1 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -1394,8 +1394,13 @@ static bool contains_pending_extent(struct btrfs_device *device, u64 *start,
static u64 dev_extent_search_start(struct btrfs_device *device, u64 start)
{
+ struct btrfs_fs_info *fs_info = device->fs_devices->fs_info;
+
switch (device->fs_devices->chunk_alloc_policy) {
case BTRFS_CHUNK_ALLOC_REGULAR:
+ if (btrfs_fs_compat_ro(fs_info, EXTRA_SUPER_RESERVED))
+ return max_t(u64, start,
+ btrfs_super_reserved_bytes(fs_info->super_copy));
return max_t(u64, start, BTRFS_DEFAULT_RESERVED);
case BTRFS_CHUNK_ALLOC_ZONED:
/*
@@ -7961,11 +7966,14 @@ static int verify_one_dev_extent(struct btrfs_fs_info *fs_info,
struct extent_map *em;
struct map_lookup *map;
struct btrfs_device *dev;
+ u32 super_reserved = BTRFS_DEFAULT_RESERVED;
u64 stripe_len;
bool found = false;
int ret = 0;
int i;
+ if (btrfs_fs_compat_ro(fs_info, EXTRA_SUPER_RESERVED))
+ super_reserved = btrfs_super_reserved_bytes(fs_info->super_copy);
read_lock(&em_tree->lock);
em = lookup_extent_mapping(em_tree, chunk_offset, 1);
read_unlock(&em_tree->lock);
@@ -7990,11 +7998,17 @@ static int verify_one_dev_extent(struct btrfs_fs_info *fs_info,
}
/*
- * Very old mkfs.btrfs (before v4.1) will not respect the reserved
- * space. Although kernel can handle it without problem, better to
- * warn the users.
+ * This can be caused by two cases:
+ * - Very old mkfs.btrfs (before v4.1) and no balance at all
+ * This should be pretty rare now, as balance will relocate
+ * those dev extents in reserved range.
+ *
+ * - Newly set btrfs_super_block::reserved_bytes
+ * We are rely on this mount to relocate those dev extents.
+ *
+ * So here, we just give a warning and continue the mount.
*/
- if (physical_offset < BTRFS_DEFAULT_RESERVED)
+ if (physical_offset < super_reserved)
btrfs_warn(fs_info,
"devid %llu physical %llu len %llu is inside the reserved space, balance is needed to solve this problem.",
devid, physical_offset, physical_len);
diff --git a/fs/btrfs/zoned.c b/fs/btrfs/zoned.c
index 7a0f8fa44800..ec16c0a6fb22 100644
--- a/fs/btrfs/zoned.c
+++ b/fs/btrfs/zoned.c
@@ -703,6 +703,14 @@ int btrfs_check_zoned_mode(struct btrfs_fs_info *fs_info)
goto out;
}
+ if (incompat_zoned && btrfs_fs_compat_ro(fs_info, EXTRA_SUPER_RESERVED)) {
+ btrfs_err(fs_info,
+ "zoned: incompatible optional feature detected: 0x%llx",
+ BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED);
+ ret = -EINVAL;
+ goto out;
+ }
+
/*
* stripe_size is always aligned to BTRFS_STRIPE_LEN in
* btrfs_create_chunk(). Since we want stripe_len == zone_size,
diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
index f54dc91e4025..4a0c9f4f55d1 100644
--- a/include/uapi/linux/btrfs.h
+++ b/include/uapi/linux/btrfs.h
@@ -290,6 +290,16 @@ struct btrfs_ioctl_fs_info_args {
#define BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE_VALID (1ULL << 1)
#define BTRFS_FEATURE_COMPAT_RO_VERITY (1ULL << 2)
+/*
+ * Allow btrfs to have extra reserved space (other than the default 1MiB) at
+ * the beginning of each device.
+ *
+ * This feature will enable the usage of btrfs_super_block::reserved_bytes.
+ *
+ * This feature would only be available for non-zoned filesystems.
+ */
+#define BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED (1ULL << 3)
+
#define BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF (1ULL << 0)
#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL (1ULL << 1)
#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 2)
--
2.36.1
^ permalink raw reply related [flat|nested] 5+ messages in thread* [PATCH DRAFT 4/4] btrfs: introduce a new experimental compat RO flag, WRITE_INTENT_BITMAP
2022-06-14 22:50 [PATCH DRAFT 0/4] btrfs: introduce the WRITE_INTENT_BITMAP compat RO flag and extra per-dev reserved space for it Qu Wenruo
` (2 preceding siblings ...)
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 ` Qu Wenruo
3 siblings, 0 replies; 5+ messages in thread
From: Qu Wenruo @ 2022-06-14 22:50 UTC (permalink / raw)
To: linux-btrfs
The new flag is for the incoming write intent bitmap, mostly to address
the RAID56 write-hole, by doing a mandatory scrub for partial written
stripes at mount time.
Currently the feature is still under development, this patch is mostly
a placeholder for the extra reserved bytes for write intent bitmap.
We will utilize the newly introduce EXTRA_SUPER_RESERVED compat RO flags
to enlarge the reserved bytes to at least (1MiB + 64KiB), and use that
64KiB (exact value is not yet fully determined) for write-intent bitmap.
Only one extra check is introduced, to ensure we have enough space to
place the write-intent bitmap at 1MiB physical offset.
This patch is only a place holder for the incoming on-disk format
change, no real write-intent functionality is implemented yet.
Signed-off-by: Qu Wenruo <wqu@suse.com>
---
fs/btrfs/ctree.h | 9 +++++++++
fs/btrfs/disk-io.c | 20 ++++++++++++++++++++
fs/btrfs/volumes.c | 14 +++++++++++++-
include/uapi/linux/btrfs.h | 7 +++++++
4 files changed, 49 insertions(+), 1 deletion(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index d29d25339c3e..1fb109f9f6b6 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -317,11 +317,20 @@ static_assert(sizeof(struct btrfs_super_block) == BTRFS_SUPER_INFO_SIZE);
#define BTRFS_FEATURE_COMPAT_SAFE_SET 0ULL
#define BTRFS_FEATURE_COMPAT_SAFE_CLEAR 0ULL
+#ifdef CONFIG_BTRFS_DEBUG
+#define BTRFS_FEATURE_COMPAT_RO_SUPP \
+ (BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE | \
+ BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE_VALID | \
+ BTRFS_FEATURE_COMPAT_RO_VERITY | \
+ BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED | \
+ BTRFS_FEATURE_COMPAT_RO_WRITE_INTENT_BITMAP)
+#else
#define BTRFS_FEATURE_COMPAT_RO_SUPP \
(BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE | \
BTRFS_FEATURE_COMPAT_RO_FREE_SPACE_TREE_VALID | \
BTRFS_FEATURE_COMPAT_RO_VERITY | \
BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED)
+#endif
#define BTRFS_FEATURE_COMPAT_RO_SAFE_SET 0ULL
#define BTRFS_FEATURE_COMPAT_RO_SAFE_CLEAR 0ULL
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index b2184fcdfde9..7c9d193a8d02 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -2825,6 +2825,26 @@ static int validate_super(struct btrfs_fs_info *fs_info,
BTRFS_DEFAULT_RESERVED);
ret = -EINVAL;
}
+ if (btrfs_super_compat_ro_flags(sb) &
+ BTRFS_FEATURE_COMPAT_RO_WRITE_INTENT_BITMAP) {
+ /* Write intent bitmap requires extra reserve. */
+ if (!(btrfs_super_compat_ro_flags(sb) &
+ BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED)) {
+ btrfs_err(fs_info,
+"WRITE_INTENT_BITMAP feature enabled, but missing EXTRA_SUPER_RESERVED feature");
+ ret = -EINVAL;
+ }
+ /*
+ * Write intent bitmap is always located at 1MiB.
+ * Extra check like the length check against the reserved space
+ * will happen at bitmap load time.
+ */
+ if (btrfs_super_reserved_bytes(sb) < BTRFS_DEFAULT_RESERVED) {
+ btrfs_err(fs_info,
+ "not enough reserved space for write intent bitmap");
+ ret = -EINVAL;
+ }
+ }
/*
* The generation is a global counter, we'll trust it more than the others
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 5c337d7ef3c1..dd523d59fe22 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -8008,11 +8008,23 @@ static int verify_one_dev_extent(struct btrfs_fs_info *fs_info,
*
* So here, we just give a warning and continue the mount.
*/
- if (physical_offset < super_reserved)
+ if (physical_offset < super_reserved) {
btrfs_warn(fs_info,
"devid %llu physical %llu len %llu is inside the reserved space, balance is needed to solve this problem.",
devid, physical_offset, physical_len);
+ /* Disable any feature relying on the new reserved_bytes. */
+ if (btrfs_fs_compat_ro(fs_info, WRITE_INTENT_BITMAP)) {
+ struct btrfs_super_block *sb = fs_info->super_copy;
+
+ btrfs_warn(fs_info,
+ "disabling write intent bitmap due to the lack of reserved space.");
+ btrfs_set_super_compat_ro_flags(sb,
+ btrfs_super_compat_ro_flags(sb) |
+ ~BTRFS_FEATURE_COMPAT_RO_WRITE_INTENT_BITMAP);
+ }
+ }
+
for (i = 0; i < map->num_stripes; i++) {
if (map->stripes[i].dev->devid == devid &&
map->stripes[i].physical == physical_offset) {
diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
index 4a0c9f4f55d1..38c74a50323e 100644
--- a/include/uapi/linux/btrfs.h
+++ b/include/uapi/linux/btrfs.h
@@ -300,6 +300,13 @@ struct btrfs_ioctl_fs_info_args {
*/
#define BTRFS_FEATURE_COMPAT_RO_EXTRA_SUPER_RESERVED (1ULL << 3)
+/*
+ * Allow btrfs to have per-device write-intent bitmap.
+ * Will be utilized to close the RAID56 write-hole (by forced scrub for dirty
+ * partial written stripes at mount time).
+ */
+#define BTRFS_FEATURE_COMPAT_RO_WRITE_INTENT_BITMAP (1ULL << 4)
+
#define BTRFS_FEATURE_INCOMPAT_MIXED_BACKREF (1ULL << 0)
#define BTRFS_FEATURE_INCOMPAT_DEFAULT_SUBVOL (1ULL << 1)
#define BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS (1ULL << 2)
--
2.36.1
^ permalink raw reply related [flat|nested] 5+ messages in thread