From: Robin Dong <sanbai@xxxxxxxxxx> After mke2fs with 1024 block size: #misc/mke2fs -m 0 -O ^resize_inode,extent,meta_bg,bigalloc -b 1024 /dev/sda kernel reports: [74687.352702] EXT4-fs (loop0): ext4_check_descriptors: Inode bitmap for group 0 not in group (block 524288)! [74687.355534] EXT4-fs (loop0): group descriptors corrupted! when mount /dev/sda. The reason is mke2fs set s_first_data_block to 0 by mistake just because s_log_cluster_size is 4 when s_log_block_size==0. This patch is based on "next" branch of e2fsprogs. Signed-off-by: Robin Dong <sanbai@xxxxxxxxxx> --- lib/ext2fs/initialize.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/ext2fs/initialize.c b/lib/ext2fs/initialize.c index ccc2dee..c2344a0 100644 --- a/lib/ext2fs/initialize.c +++ b/lib/ext2fs/initialize.c @@ -155,7 +155,7 @@ errcode_t ext2fs_initialize(const char *name, int flags, } else super->s_log_cluster_size = super->s_log_block_size; - set_field(s_first_data_block, super->s_log_cluster_size ? 0 : 1); + set_field(s_first_data_block, super->s_log_block_size ? 0 : 1); set_field(s_max_mnt_count, 0); set_field(s_errors, EXT2_ERRORS_DEFAULT); set_field(s_feature_compat, 0); -- 1.7.3.2 -- 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