Jeff Mings wrote:
I've noticed that fsck.ext2 and fsck.ext3 are identical - try checking them with the cmp command if you're really bored. I've fixed messed up ext3 volumes with e2fsck -cfv a few times - I don't believe that you really have to worry about the journal.
Worst comes to worst, you should be able to use e2fsck on it (as if it were ext2) then completely rebuild the journal (using the same options that you use to convert ext2 to ext3).
Good luck, -Jeff
--MonMotha
