https://community.hpe.com/t5/operating-system-linux/aborting-journal/m-p/4347534#M35043 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. Thu, 29 Jan 2009 15:57:44 GMT Heironimus 2009-01-29T15:57:44Z https://community.hpe.com/t5/operating-system-linux/aborting-journal/m-p/4347533#M35042 This is the error:<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150): ext3_free_blocks_sb: bit already cleared for block 2223200<BR />Jan 27 12:28:18 myhost123 kernel: Aborting journal on device dm-150.<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_free_blocks_sb: Journal has aborted<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_reserve_inode_write: Journal has aborted<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_reserve_inode_write: Journal has aborted<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_orphan_del: Journal has aborted<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150) in ext3_truncate: Journal has aborted<BR />Jan 27 12:28:18 myhost123 kernel: ext3_abort called.<BR />Jan 27 12:28:18 myhost123 kernel: EXT3-fs error (device dm-150): ext3_journal_start_sb: Detected aborted journal<BR />Jan 27 12:28:18 myhost123 kernel: Remounting filesystem read-only<BR />Jan 27 12:28:18 myhost123 kernel: __journal_remove_journal_head: freeing b_committed_data<BR />Jan 27 12:28:58 myhost123 kernel: program nmhs is using a deprecated SCSI ioctl, please convert it to SG_IO<BR />Jan 27 13:48:22 myhost123 last message repeated 7322 times<BR />Jan 27 13:48:33 myhost123 last message repeated 7321 times<BR />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<BR /><BR />Kernel version:<BR />2.6.18-92.1.13.el5<BR /><BR />OS:<BR />Red Hat Enterprise Linux Server release 5.2 (Tikanga)<BR /><BR />The SAN disk has no error this is from my point of view a kernel error. Do anyone know which patch to apply?<BR /><BR />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.<BR /><BR />/JT Thu, 29 Jan 2009 14:28:51 GMT https://community.hpe.com/t5/operating-system-linux/aborting-journal/m-p/4347533#M35042 Jannik 2009-01-29T14:28:51Z https://community.hpe.com/t5/operating-system-linux/aborting-journal/m-p/4347534#M35043 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. Thu, 29 Jan 2009 15:57:44 GMT https://community.hpe.com/t5/operating-system-linux/aborting-journal/m-p/4347534#M35043 Heironimus 2009-01-29T15:57:44Z