Issue

• An ext3 filesystem goes into readonly mode frequently with the following error in log file :

  kernel: EXT3-fs error (device sda3): ext3_free_blocks_sb: bit already cleared for block 1652749
  kernel: Aborting journal on device sda3.
  kernel: EXT3-fs error (device sda3) in ext3_orphan_del: Journal has aborted
  kernel: EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
  kernel: EXT3-fs error (device sda3) in ext3_delete_inode: Journal has aborted
  kernel: __journal_remove_journal_head: freeing b_committed_data
  kernel: EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal
  kernel: Remounting filesystem read-only
  

• Filesystem journal abort happens with the message "ext3_free_blocks_sb: bit already cleared for block ", why?

• A LUN presented from an IBM DS8300 storage to the server as ext3 filesystem got mounted in read-only mode.
• In some cases the LUN may also be mounted on another server.