Hi Ted, I have been exploring the possibility to make exclude bitmap a compat feature and I think I have come to a dead end with ext4_init_block_bitmap(). On old kernels, this function will disregard the exclude bitmap block and leave it free in the block bitmap. So that leaves us with the less attractive option to make it rocompat, which leads to the following dilemma: Once exclude bitmap is allocated by new mkfs or added by new tune2fs, the fs can no longer be mounted by an older kernel. How can we solve that problem? We could use 2 features: EXT4_FEATURE_COMPAT_EXCLUDE_BITMAP /* exclude bitmap is allocated */ EXT4_FEATURE_RO_COMPAT_UNINIT_EXCLUDE /* uninit_bg and exclude_bitmap are set */ New mkfs can allocate exclude bitmaps for uninit groups and set the 2 features by default. tune2fs -O ^uninit_exclude can init all groups and remove the rocompat feature, making the fs available for old kernels, while keeping the exclude bitmap intact. Does that make sense to you? Amir. -- 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
