Messages in this thread | | | Date | Fri, 4 Apr 2003 19:49:02 -0700 | From | Andreas Dilger <> | Subject | Re: Can't recover from broken ext3 journal |
| |
On Mar 26, 2003 01:30 -0800, brian@worldcontrol.com wrote: > I had a harddrive develop hard IO errors in the section of the drive > that holds the ext3 journal. > > If it try to fsck the filesystem, fsck eventually terminates after > trying to replay the journal. > > I tried to use debugfs but that fails in similar way. > > When I use tune2fs to try to turn off the journal, even with > the -f option, it simply reports 'the needs_recovery flag is > set, please run e2fsck'. > > I've replaced the drive and restored from backups, however, it seems > rather poor design that I should lose *all* my data on the drive simply > because the journal won't replay due to an disk error.
debugfs -w -R "feature ^has_journal ^needs_recovery" /dev/whatever e2fsck -f /dev/whatever
Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |