Re: Ext3 problems (aborting journal).

Andreas Dilger
2004-04-29T17:09:27Z

On Apr 29, 2004 14:15 +0200, David Martínez Moreno wrote:
> Hello all. I'm writing to all the people in charge of ext3 fs
>
> Apr 29 12:21:21 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone - block = 1071716394, count = 1

You need to run "e2fsck -f /dev/sda7" on the unmounted filesystem. There
is some sort of corruption there.

> Apr 23 20:35:41 arsinoe kernel: EXT3-fs error (device sda7): ext3_free_blocks: Freeing blocks not in datazone - block = 1075532092, count = 1

This earlier error should have forced a full fsck - did that run?

> Apr 23 20:38:47 arsinoe kernel: i91u: Reset SCSI Bus ...
> Apr 23 20:38:47 arsinoe kernel: ERROR: SCSI host `INI9100U' has no error handling
> Apr 23 20:38:47 arsinoe kernel: ERROR: This is not a safe way to run your SCSI host
> Apr 23 20:38:47 arsinoe kernel: ERROR: The error handling must be added to this driver

This seems a bit ominous, not sure how bad it really is.

> I forced to fsck all the ext3 drives (/dev/sda{1,6,7}) and installed 2.6.6-rc2.
> It fsck'ed one of the partitions, then wanted to reboot, then fsck'ed the three

Hmm, so it did run. It seems you are getting corruption on the disk for
some reason.

> A tune2fs from the affected partition:
>
> arsinoe:/usr/src/dev# tune2fs -l /dev/sda7
> tune2fs 1.35-WIP (07-Dec-2003)
> Filesystem volume name: <none>
> Last mounted on: <not available>
> Filesystem UUID: 6b9d38e7-7487-444b-b8e4-68404673964f
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: has_journal filetype needs_recovery sparse_super
> Default mount options: (none)
> Filesystem state: clean with errors

Was this after the e2fsck was run? It shouldn't be marked "with errors".

Cheers, Andreas
--
Andreas Dilger