Aborted journal and volume remounted read-only

Aborted journal and volume remounted read-only
I have errors like this in my messages file, and nobody can write to the volume its talking about. i’m assuming i need to reboot and do an e2fsck but what options would you recommend? -fyc i’m thinking but not sure. thanks for the help!!

journal_bmap: journal block not found at offset 5132 on hdb5
Aborting journal on device hdb5.
__journal_remove_journal_head: freeing b_committed_data
journal commit I/O error
ext3_abort called.
EXT3-fs error (device hdb5): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only

========================

Actually, what you need to do is remove the journal from the filesystem and then do the e2fsck -f. Then readd the journal and reboot. Of course to do all this you need the filesystem unmounted.

tune2fs -O ^has_journal /dev/
e2fsck -f /dev/
tune2fs -j /dev/

========================
From: http://linux.ittoolbox.com/groups/technical-functional/redhat-l/ext3-file-system-remoting-read-only-journal-aborting-2122208

Every time Im repairing file system and following below steps
1. Unmounting the file system (/disk1)

1. Nuke the ext3 journal
   tune2fs -O ^has_journal /dev/

2. e2fsck -fy /dev/sdc14

3. Rebuild the journal
   tune2fs -j /dev/sdc14

4. Mounting the file system (/disk1)