当文件系统变因为Detected aborted journal时filesystem read-only的解决方法

真麻烦,一个机器有4个7T的存储中有二个存储有问题，用fsck修复了三次，都没有反应。使用使用着就提示下面的出错

#dmesg

EXT3-fs error (device sdh1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdh1): ext3_lookup: unlinked inode 67584015 in dir #6758401

然后使用着那个挂的分区就变成只读read-only.

后来找到了e2fsck，还是蛮不错的。最少他能修复.

#umount  /dev/sdg1
#e2fsck       -y          /dev/sdg1

e2fsck 1.39 (29-May-2006)
/data: recovering journal
/data contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 286556161, i_size is 512000, should be 520192.  Fix? yes

Inode 286556161, i_blocks is 984, should be 1024.  Fix? yes

Pass 2: Checking directory structure
Entry ‘[M-fM-^IM-^QM-eM-^EM-^KM-gM-^NM-^KM-oM-<M-^MM-gM->M-^NM-eM-^FM-^[M-fM-4M-;M-fM-^MM-^IM-hM-^PM-(M-hM->M->M-eM-'M-^FM-eM-.M-^^M-eM-=M-^U].Ace.In.The.Hole.2005.DVDRip.XviD-LAJH.AC3.CD-1.avi’ in /mldonkey1/M-fM-^IM-^QM-eM-^EM-^KM-gM-^NM-^KM-oM-<M-^MM-gM->M-^NM-eM-^FM-^[M-fM-4M-;M-fM-^MM-^IM-hM-^PM-(M-hM->M->M-eM-’M-^FM-eM-.M-^^M-eM-=M-^U (820150293) has deleted/unused inode 820150302.  Clear? yes

Problem in HTREE directory inode 286556161: node (122) has bad min hash
Problem in HTREE directory inode 286556161: node (122) referenced twice
Problem in HTREE directory inode 286556161: node (123) referenced twice
Problem in HTREE directory inode 286556161: node (124) referenced twice
Invalid HTREE directory inode 286556161 (/rss/xinhuanet/video/20092).  Clear? yes
 

 

这样，但1T的文件大约需要1个小时。。。我花了6个小时才检查修复完6T .

象这样的文件系统坏，出现问题，要从二个方面入手，一个是软件，一个是硬件。

1.查看日志,dmesg和tail -f /var/log/messages
2.要看日志检查相关的内容和软硬件
3.还没有结果就google看看有没有人和你一样出现这个问题。看看别人是怎么处理。
4.换硬件。比如RAID卡之类。