IIRC you can treat it as an ext2 partition ( tune2fs <device> -O ^has_journal switches it off ), and fsck it ( -b 32 always helps if you have problems ). Then you can mount it as ext2, and drop the journals ( rm <mount point>/.journal ). Once you've got it clean, you can reset it to ext3 again with tune2fs, and mounting it recerates the journals.
Dunno if that's any use to you. Steve On Fri, 08 Sep 2006 13:36:11 +1200 "Davidson, Brett (Managed Services)" <[EMAIL PROTECTED]> wrote: > 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] > > >
