cancel
Showing results for 
Search instead for 
Did you mean: 

Aborting journal

 
SOLVED
Go to solution
Jannik
Honored Contributor

Aborting journal

This is the error:
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150): ext3_free_blocks_sb: bit already cleared for block 2223200
Jan 27 12:28:18 myhost123 kernel: Aborting journal on device dm-150.
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_free_blocks_sb: Journal has aborted
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_reserve_inode_write: Journal has aborted
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_reserve_inode_write: Journal has aborted
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_orphan_del: Journal has aborted
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_truncate: Journal has aborted
Jan 27 12:28:18 myhost123 kernel: ext3_abort called.
Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150): ext3_journal_start_sb: Detected aborted journal
Jan 27 12:28:18 myhost123 kernel: Remounting filesystem read-only
Jan 27 12:28:18 myhost123 kernel: __journal_remove_journal_head: freeing b_committed_data
Jan 27 12:28:58 myhost123 kernel: program nmhs is using a deprecated SCSI ioctl, please convert it to SG_IO
Jan 27 13:48:22 myhost123 last message repeated 7322 times
Jan 27 13:48:33 myhost123 last message repeated 7321 times
Jan 27 14:21:19 myhost123 dsmc: ANS1398E Initialization functions cannot open one of the Tivoli Storage Manager logs or a related file: /smpitp/logs/SCHED.LOG. errno = 30, Read-only file system

Kernel version:
2.6.18-92.1.13.el5

OS:
Red Hat Enterprise Linux Server release 5.2 (Tikanga)

The SAN disk has no error this is from my point of view a kernel error. Do anyone know which patch to apply?

I fixed it by unmount and e2fsck the volume but that don't really go for i high uptime database, where I really need to min the downtime.

/JT
jaton
1 REPLY
Heironimus
Honored Contributor
Solution

Re: Aborting journal

All those messages mean is that the filesystem was already corrupted. They say nothing about the cause, which may have happened at some earlier time.