免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
123下一页
最近访问板块 发新帖
查看: 20392 | 回复: 25
打印 上一主题 下一主题

最近系统老是损坏文件系统,大家帮忙看看,谢谢! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2011-04-14 11:47 |只看该作者 |倒序浏览
EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131

Apr 10 03:15:02  kernel: EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131
Apr 11 03:33:02  kernel: EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131
Apr 11 15:22:20  kernel: php-cgi[5609]: segfault at 0 ip 00007fc170fc8a09 sp 00007fff82384ea0 error 4 in pdo_pgsql.so[7fc170fc2000+8000]
Apr 12 03:32:02  kernel: EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131
Apr 13 03:38:01  kernel: EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131
Apr 14 11:06:13  kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Apr 14 11:06:22  kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
Apr 14 11:06:22 kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
Apr 14 11:06:22 kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
Apr 14 11:06:42 kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #69380: directory entry across blocks - offset=12, inode=69374, rec_len=4356, name_len=35
Apr 14 11:12:54 kernel: EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 57131


--------------------------------------------------------
运行fsck也不行,有时直接重启一下就会出现损坏

论坛徽章:
0
2 [报告]
发表于 2011-04-14 13:54 |只看该作者
初步怀疑会不会是i/owait造成的问题

论坛徽章:
36
IT运维版块每日发帖之星
日期:2016-04-10 06:20:00IT运维版块每日发帖之星
日期:2016-04-16 06:20:0015-16赛季CBA联赛之广东
日期:2016-04-16 19:59:32IT运维版块每日发帖之星
日期:2016-04-18 06:20:00IT运维版块每日发帖之星
日期:2016-04-19 06:20:00每日论坛发贴之星
日期:2016-04-19 06:20:00IT运维版块每日发帖之星
日期:2016-04-25 06:20:00IT运维版块每日发帖之星
日期:2016-05-06 06:20:00IT运维版块每日发帖之星
日期:2016-05-08 06:20:00IT运维版块每日发帖之星
日期:2016-05-13 06:20:00IT运维版块每日发帖之星
日期:2016-05-28 06:20:00每日论坛发贴之星
日期:2016-05-28 06:20:00
3 [报告]
发表于 2011-04-14 14:48 |只看该作者
看一下磁盘的  read ahead

论坛徽章:
0
4 [报告]
发表于 2011-04-14 14:55 |只看该作者
主要是在内态模块里一直写文件

论坛徽章:
0
5 [报告]
发表于 2011-04-14 15:50 |只看该作者
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Unhandled sense code
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Apr 13 09:29:52   kernel: Descriptor sense data with sense descriptors (in hex):
Apr 13 09:29:52   kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Apr 13 09:29:52   kernel:        00 8a 7f ff
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
Apr 13 09:29:52   kernel: end_request: I/O error, dev sda, sector 9076735
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Unhandled sense code
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Apr 13 09:29:52   kernel: Descriptor sense data with sense descriptors (in hex):
Apr 13 09:29:52   kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Apr 13 09:29:52   kernel:        00 8a 7f ff
Apr 13 09:29:52   kernel: sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
Apr 13 09:29:52   kernel: end_request: I/O error, dev sda, sector 9076735
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: NET: Registered protocol family 10
Apr 13 09:29:52   kernel: lo: Disabled Privacy Extensions
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)
Apr 13 09:29:52   kernel: ata1.00: status: { DRDY ERR }
Apr 13 09:29:52   kernel: ata1.00: error: { UNC }
Apr 13 09:29:52   kernel: ata1.00: configured for UDMA/133
Apr 13 09:29:52   kernel: ata1: EH complete
Apr 13 09:29:52   kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 13 09:29:52   kernel: ata1.00: irq_stat 0x40000001
Apr 13 09:29:52   kernel: ata1.00: cmd c8/00:08:ff:7f:8a/00:00:00:00:00/e0 tag 0 dma 4096 in
Apr 13 09:29:52   kernel:         res 51/40:00:ff:7f:8a/f1:00:00:00:00/e0 Emask 0x9 (media error)

论坛徽章:
0
6 [报告]
发表于 2011-04-15 08:28 |只看该作者
是磁盘出错吗?

在内核态写文件,如果程序没有问题,不会引起文件系统问题的。

论坛徽章:
0
7 [报告]
发表于 2011-04-15 09:40 |只看该作者
avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           6.04    0.00   13.42    0.17    0.00   80.37

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sda               0.00     9.67    0.00   19.33     0.00   232.00    12.00     0.05    2.50   0.14   0.27

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           2.98    0.00    2.32    0.83    0.00   93.87

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sda               0.00     0.00    1.67    0.00    21.33     0.00    12.80     0.02    9.20  10.60   1.77

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           7.62    0.00   14.07   13.41    0.00   64.90

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sda               1.67    33.67  170.00   30.00 23805.33   512.00   121.59     1.34    6.70   1.75  34.93

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           2.17    0.00    2.17   11.52    0.00   84.14

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
sda               4.67   176.67   87.00   36.67 12360.00  1717.33   113.83     3.27   26.41   1.99  24.67

论坛徽章:
0
8 [报告]
发表于 2011-04-15 09:42 |只看该作者
会不会有可能是写硬盘中IO中等待的太多,导致脏数据,或者缓冲区污染导致文件节点出问题了呢?

论坛徽章:
36
IT运维版块每日发帖之星
日期:2016-04-10 06:20:00IT运维版块每日发帖之星
日期:2016-04-16 06:20:0015-16赛季CBA联赛之广东
日期:2016-04-16 19:59:32IT运维版块每日发帖之星
日期:2016-04-18 06:20:00IT运维版块每日发帖之星
日期:2016-04-19 06:20:00每日论坛发贴之星
日期:2016-04-19 06:20:00IT运维版块每日发帖之星
日期:2016-04-25 06:20:00IT运维版块每日发帖之星
日期:2016-05-06 06:20:00IT运维版块每日发帖之星
日期:2016-05-08 06:20:00IT运维版块每日发帖之星
日期:2016-05-13 06:20:00IT运维版块每日发帖之星
日期:2016-05-28 06:20:00每日论坛发贴之星
日期:2016-05-28 06:20:00
9 [报告]
发表于 2011-04-15 09:48 |只看该作者
嗯,建议查找一下磁盘读写(主要是写入)优化的参数,然后做一些测试

论坛徽章:
0
10 [报告]
发表于 2011-04-23 05:40 |只看该作者
我也遇到这种问题了,我开始以为硬盘的问题,换了新硬盘。换新硬盘后半个月没有问题,但是后来我加上了APACHE的访问日志入库的crontab程序,昨天又修改了一个数据库频繁读数据的排序顺序(从 ASC 改为 DESC),改了没多久,文件系统就出问题了。我这个情况是不是可以验证您说的观点呢。如果我不加apache日志的入库程序,服务器坚持跑的时间会不会就长一些?然后,怎样避免或解决这种问题呢?我的服务器是IBM X336,硬盘是普通的PC硬盘,希捷SATA 500G
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP