解决挂载盘柜出现“EXT3-fs error filesystem read-only”

    昨天发现盘柜上的逻辑卷只能读，不能写！，查看盘柜管理页面，无错误提示，盘柜上面的硬盘指示灯也是正常的，查看前端的挂载机器的系统日志信息/var/log/messages，错误信息如下：

EXT3-fs error (device sdc1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_truncate: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_delete_inode: Journal has aborted

EXT3-fs warning (device sdb1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sdb1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369513
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369514
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369515
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369516
ext3_abort called.
EXT3-fs error (device sdc1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_truncate: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_delete_inode: Journal has aborted




从错误的信息来看，初步判断是由于ext3文件系统的日志引起的，当内核检测到ext3文件系统的日志有问题，就报警，严重的就将改分区挂载为只读模式。

下面开始着手解决这个问题：
1，首先用fsck检查改分区的文件系统
   当用fsck命令检查该分区后，重新启动系统，系统还是报这样的错误。
2，看来“病”的不轻，想过用第一张启动盘进入救援模式修复，但是一想，不对，没办法识别到额外挂载的
   设备，因为此时网络还有启动。
3，看来只能用苯方法，将数据备份出来，重新格式化了，结果重新格式化后，解决问题。


总结：
    文件系统损坏有几个原因，一个是非法关机，第二个是磁盘有环道，只能一个一个排除，先软后硬，如果格式化后，还是有问题，那原因多半就是硬件的问题了。同时提醒兄弟们，多半的原因是由于非法关机引起的，比如冷启动，运气好的话，没有异常出现，否则，哈哈，你的麻烦来了。 希望兄弟们少走一些弯路，操作一定要规范！！！