This can be caused by tune2fs -O flex_bg. And clearing flex_bg on such
partitions is harmless.
Signed-off-by: Peng Tao <bergwolf@xxxxxxxxx>
---
misc/tune2fs.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/misc/tune2fs.c b/misc/tune2fs.c
index 887a702..f7373af 100644
--- a/misc/tune2fs.c
+++ b/misc/tune2fs.c
@@ -407,7 +407,8 @@ static void update_feature_set(ext2_filsys fs, char *features)
uuid_generate((unsigned char *) sb->s_hash_seed);
}
- if (FEATURE_OFF(E2P_FEATURE_INCOMPAT, EXT4_FEATURE_INCOMPAT_FLEX_BG)) {
+ if (FEATURE_OFF(E2P_FEATURE_INCOMPAT, EXT4_FEATURE_INCOMPAT_FLEX_BG) &&
+ sb->s_log_groups_per_flex) {
if (ext2fs_check_desc(fs)) {
fputs(_("Clearing the flex_bg flag would "
"cause the the filesystem to be\n"
--
1.6.1.3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
