On Oct 28, 2002 14:00 -0500, Steve McGrane wrote: > Any news on how to remove a reference to a non-existent .journal file? Running "e2fsck -f /dev/hda7" should remove the bad journal from the superblock. > -----Original Message----- > From: ext3-users-admin@redhat.com [mailto:ext3-users-admin@redhat.com]On > Behalf Of Steve McGrane > Sent: Thursday, October 24, 2002 7:57 PM > To: ext3-users@redhat.com > Subject: Cannot remove Journal Pointer > > > I recently had an EXT3 system that went belly-up. The drive would complain > "Can't write to FS" > > Oct 21 04:23:29 starline kernel: hda: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Oct 21 04:23:29 starline kernel: hda: dma_intr: error=0x40 { > UncorrectableError }, LBAsect=19419072, sector=12488 > Oct 21 04:23:29 starline kernel: end_request: I/O error, dev 03:07 (hda), > sector 12488 > Oct 21 04:23:29 starline kernel: journal_bmap: journal block not found at > offset 1036 on ide0(3,7) > Oct 21 04:23:29 starline kernel: Aborting journal on device ide0(3,7). > Oct 21 04:23:29 starline kernel: ext3_abort called. > Oct 21 04:23:29 starline kernel: EXT3-fs abort (device ide0(3,7)): > ext3_journal_start: Detected aborted journal > Oct 21 04:23:29 starline kernel: Remounting filesystem read-only > > "mount" would show the FS as read-only, and fsck would fix tons of errors. > fsck replaced the inode that the .journal file was in and this created tons > of errors: > > Oct 21 15:36:47 starline kernel: end_request: I/O error, dev 03:07 (hda), > sector 12480 > Oct 21 15:36:47 starline kernel: journal_bmap: journal block not found at > offset 1036 on ide0(3,7) > Oct 21 15:36:47 starline kernel: Aborting journal on device ide0(3,7). > Oct 21 15:36:47 starline kernel: ext3_abort called. > Oct 21 15:36:47 starline kernel: EXT3-fs abort (device ide0(3,7)): > ext3_journal_start: Detected aborted journal > > We tried to remove the journal with the standard command, and it failed. We > tried to create a new journal and that failed as well with "Journal Exists". > We couldn't mount the fs as EXT2, so we had to copy the data off, mkfs, > re-apply the ext3 journal and recopy the data over. > > What are the recovery options/procedures when the journal is missing but the > tune2fs program still thinks they are there? Is there a force option? Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/ _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
