btrfs-progs: mkfs: Make no-holes as default mkfs incompat features
PATCH 1/1 btrfs-progs: mkfs: Make no-holes as default mkfs incompat features
No-holes feature could save 53 bytes for each hole we have, and it provides a pretty good workaround to prevent btrfs check from reporting non-contiguous file extent holes for mixed direct/buffered IO.
The latter feature is more helpful for developers for handle log-writes based test cases.
Signed-off-by Qu Wenruo <[email protected]>
--- common/fsfeatures.c | 2 +- common/fsfeatures.h | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-)
common/fsfeatures.c +1 -1
@@ -84,7 +84,7 @@ static const struct btrfs_fs_feature {"no_holes" ,VERSION_TO_STRING2 (3 ,14 ),VERSION_TO_STRING2 (4 ,0 ), -NULL ,0 , +VERSION_TO_STRING2 (5 ,4 ), "no explicit hole extents for files" },/* Keep this one last */ { "list-all", BTRFS_FEATURE_LIST_ALL, NULL }
common/fsfeatures.h +3 -2
@@ -21,8 +21,9 @@#define BTRFS_MKFS_DEFAULT_NODE_SIZE SZ_16K#define BTRFS_MKFS_DEFAULT_FEATURES \ - (BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF \ - | BTRFS_FEATURE_INCOMPAT_SKINNY_METADATA) + (BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF | \ + BTRFS_FEATURE_INCOMPAT_SKINNY_METADATA | \ + BTRFS_FEATURE_INCOMPAT_NO_HOLES)/* * Avoid multi-device features (RAID56) and mixed block groups
Signature · 1 line
2.24.0