Hello all.
The subject of the message might sound kindof silly, but really, what cause or what do I need to look for to prevent the errors that happen to a file system and that you can only repair with a manual fsck?
One of my filesystems marked itself as read-only after the following error ocurred (from /var/log/messages)(I separated eac line for readability):
Code:
qonos kernel: EXT3-fs error (device sda7): ext3_free_blocks_sb: bit already cleared for block 107446800
qonos kernel: Aborting journal on device sda7. Sep 21 09:12:41 qonos kernel: ext3_abort called.
qonos kernel: EXT3-fs error (device sda7): ext3_journal_start_sb: Detected aborted journal
qonos kernel: Remounting filesystem read-only
qonos kernel: ext3_free_inode: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device sda7) in ext3_free_inode: Journal has aborted Sep 21 09:12:41 qonos kernel: EXT3-fs error (device sda7) in ext3_delete_inode: Journal has aborted
qonos kernel: __journal_remove_journal_head: freeing b_committed_data
After this happened, nobody could access it. I had to run fsck.ext3 -As manually to fix the errors.
Any advice or pointing to the right direction will be greatly appreciated.
Tony.
~~~~
"Sysadmin is like keeping the trains on time: Nobody notices until they're late"