Anyone confronted
the issue where a machine lost power and both the journal and ext filesystem
underneath have errors?
To fix the ext3
filesystem, fsck normally applies the journal first but as that's also corrupt,
things don't play.
I have restored the
system from the last backup but have kept a "dd" of the filesystem so I can play
later as a loopback.
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.
Should I delete the
filesystem copy as there is absolutely nothgin to be done or is there some fun
learning to be had?
Brett.
Brett Davidson : RHCE, MCSE, SCSA,
NZCE(Electronics&Computing), TC(Electronics)
Systems Support
Specialist
HP Christchurch, New Zealand
Phone : +64 3 962 5773
Fax
: +64 3 962 5747
Email : [EMAIL PROTECTED]
