# tune2fs -f -O ^has_journal sda1.img tune2fs 1.41.12 (17-May-2010) The needs_recovery flag is set. Please run e2fsck before clearing the has_journal flag. nope, not even with force. Grr. Maybe this will work; get the journal inode number & clear it: # dumpe2fs -h sda1.img | grep "Journal inode" dumpe2fs 1.41.12 (17-May-2010) Journal inode: 8 # debugfs -w -R "clri <8>" sda1.img now e2fsck will think the journal is invalid & just zap it: e2fsck 1.41.12 (17-May-2010) Superblock has an invalid journal (inode 8). Clear<y>? *maybe* that will get your e2fsck past the journal recovery problem w/o needing the mkfs.ext4 -S giant hammer.
Why not just unset the journal feature bit using debugfs? debugfs -w -R "features ^has_journal" sda1.img And I would update e2fsprogs to the current version. Cheers, Bernd -- 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
