Hi Jan, >My first guess would be that journal superblock was corrupted by >fsfuzzer so that the journal had less than 32 blocks and the warning >triggered. That being said, we might use more sanity checks when loading >journal superblock because currently it just blindly consumes what's on >disk. We can't do too much since we don't know anything about the >filesystem structure but we can do at least something. I'll write a >patch for that in a moment... Any updates on this. Thanks!! Regards R.Nageswara Sastry -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
