Davidson, Brett (Managed Services) wrote:
Anyone confronted the issue where a machine lost power and both the journal and ext filesystem underneath have errors?
err, no.
To fix the ext3 filesystem, fsck normally applies the journal first but as that's also corrupt, things don't play.
what does tune2fs -O^has_journal /dev/.... do?
It appears that the journal starts at block 0 and debugfs won't let you touch block 0 so I can't just remove the inode and/or the journal file.
hmm. could be fubar. Cheers, Rex
