resize2fs seems to come up with some crazy default stride numbers. This occurs with and without bigalloc. I was testing enabling/disabling 64bit using latest patches from DJW, and noticed that s_raid_stride was being written with nonsensical values, in particular determine_fs_stride() is coming up with overly large values. The code is old (2006) and lacks comment so I'm not sure what the intended operation is. Does this just need to be updated for flex_bg? Should s_raid_stride ever be auto-changed on resize? If it should change, should stripe also change? +Reardon -- 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
