On Sep 22, 2005 00:53 -0400, Eric Lammerts wrote: > journal_bmap: journal block not found at offset 1036 on hda6 > Aborting journal on device hda6. > ext3_abort called. > > The filesystem is mounted with errors=panic, so the system reboots. At > boot-up an e2fsck is run on /dev/hda6. Sometimes it finds errors, > sometimes not. Example: > > e2fsck 1.35 (28-Feb-2004) > data: recovering journal > data contains a file system with errors, check forced. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > Free blocks count wrong for group #73 (26, counted=0). > Fix? yes > Free blocks count wrong for group #74 (5071, counted=667). > Fix? yes > Free blocks count wrong for group #75 (3585, counted=2844). > Fix? yes > Free blocks count wrong (1503376, counted=1498205). > Fix? yes > data: ***** FILE SYSTEM WAS MODIFIED ***** > data: 1960/1343488 files (34.2% non-contiguous), 1186650/2684855 > blocks > > But soon after that, the same kernel message happens again. > I've also tried a newer e2fsck, from the e2fsck-static 1.38-2 Debian > package, but that one didn't solve the problem either. This sounds a LOT like your disk is going bad. Having e2fsck fix problems like this, then immediately getting errors again is something I've seen in the past and it turned out that the disk was flaky. Try running "badblocks" on the disk in non-destructive write mode and see what it finds. I'd strongly recommend a backup at this point if you don't already have it. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
