There is no extended irefs in the new fs, and we can mount it on
the old kernel without extended iref function safely. So we needn't
set INCOMPAT_EXTENDED_IREF flag when making a new fs, and just set
it when we actually insert a extended iref.
Signed-off-by: Miao Xie <mi...@cn.fujitsu.com>
Cc: Mark Fasheh <mfas...@suse.de>
---
mkfs.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mkfs.c b/mkfs.c
index c8cb395..aca6e46 100644
--- a/mkfs.c
+++ b/mkfs.c
@@ -1654,8 +1654,6 @@ raid_groups:
super = root->fs_info->super_copy;
flags = btrfs_super_incompat_flags(super);
- flags |= BTRFS_FEATURE_INCOMPAT_EXTENDED_IREF;
-
if (mixed)
flags |= BTRFS_FEATURE_INCOMPAT_MIXED_GROUPS;
--
1.8.0.1
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
