Filesystem became readonly when try to write something

Solution Verified - Updated -

Issue

  • System became readonly with the below error messages in /var/log/messages
# tail /var/log/messages
Oct 21 15:00:53 localhost kernel: kjournald starting.  Commit interval 5 seconds
Oct 21 15:00:53 localhost kernel: EXT3 FS on dm-15, internal journal
Oct 21 15:00:53 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Oct 21 15:05:33 localhost kernel: EXT3-fs error (device dm-15): read_inode_bitmap: Cannot read inode bitmap - block_group = 367, inode_bitmap = 12025857
Oct 21 15:05:33 localhost kernel: Aborting journal on device dm-15.
Oct 21 15:05:33 localhost kernel: EXT3-fs error (device dm-15) in ext3_new_inode: IO failure
Oct 21 15:05:34 localhost kernel: EXT3-fs error (device dm-15) in ext3_mkdir: IO failure
Oct 21 15:05:34 localhost kernel: ext3_abort called.
Oct 21 15:05:34 localhost kernel: EXT3-fs error (device dm-15): ext3_journal_start_sb: Detected aborted journal
Oct 21 15:05:34 localhost kernel: Remounting filesystem read-only

Environment

  • Red Hat Enterprise Linux

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.