PROBLEM: log abort over RAID5

Bodo Thiesen bothie at
Fri Mar 5 16:18:05 UTC 2004

Leandro Guimarães Faria Corsetti Dutra <leandro at> wrote:

>	After I/O, journal is aborted and filesystems made read-only.
>	One can't anymore write to the affected file systems.  Upon
>investigation, ext3fs journal was aborted and affected filesystems are
>remounted read-only.  Reboot prompts for fsck to be run manually, with
>fixes taking several prompts and minutes.

>Feb 26 06:25:24 mercurio kernel: EXT3-fs error (device dm-2):
>ext3_readdir: bad entry in directory #381585: directory entry across
>blocks - offset=0, inode=0, rec_len=4132, name_len=63 Feb 26 06:25:24
>mercurio kernel: Aborting journal on device dm-2. Feb 26 06:25:24 mercurio
>kernel: ext3_abort called. Feb 26 06:25:24 mercurio kernel: EXT3-fs abort
>(device dm-2): ext3_journal_start: Detected aborted journal Feb 26
>06:25:24 mercurio kernel: Remounting filesystem read-only [...]
>Feb 26 15:57:21 mercurio kernel: EXT3-fs error (device dm-2) in
>start_transaction: Journal has aborted Feb 26 15:57:21 mercurio kernel:
>EXT3-fs error (device dm-2) in ext3_delete_inode: Journal has aborted

1. Check if the hard disk has bad blocks.

# badblocks -b <ext3blocksize> <ext3device>

If you have errors here, than ask again what to do in this list - I don't 
know how to recover from errors like bad blocks in the journal ;-)

Assuming badblocks didn't report any errors, continue:

2. Umount the filesystem

3. Run e2fsck

   If that fails, report it here and don't continue ;-)

4. Try to remount the filesystem as ext3.

   If that works, you should be done.

5. If that doesn't work then:

   Report the error messages here. You may continue or wait for answers ...

6. disable usage of journal: tune2fs -O ^has_journal <ext3device>

7. mount the file system as ext2 and update /etc/fstab according to that.

Regards, Bodo

More information about the Ext3-users mailing list