- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Aborting journal
Operating System - Linux
1753394
Members
7179
Online
108792
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2009 06:28 AM
01-29-2009 06:28 AM
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
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
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2009 07:57 AM
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP