免费注册 查看新帖 |

Chinaunix

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

mysql出现崩溃,求原因 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2010-11-11 17:28 |只看该作者 |倒序浏览
请问造成崩溃的原因。

错误日志如下:
-----------------------------
101110 23:52:14  InnoDB: Page checksum 3123610979, prior-to-4.0.14-form checksum 1090887538
InnoDB: stored checksum 641667391, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 501 2805892917, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 218281,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 123
InnoDB: Page may be an index page where index id is 0 303
InnoDB: (index "PRIMARY" of table "customers"."name")
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 218281.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
101110 23:52:14 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=33554432
read_buffer_size=8388608
max_used_connections=949
max_threads=151
threads_connected=32
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1939154 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
101110 23:52:15 mysqld_safe Number of processes running now: 0
101110 23:52:15 mysqld_safe mysqld restarted
101110 23:52:16 [Note] Plugin 'FEDERATED' is disabled.
101110 23:52:16 [Note] Plugin 'ndbcluster' is disabled.
InnoDB: Log scan progressed past the checkpoint lsn 1053 388313431
101110 23:52:19  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1053 393555968
InnoDB: Doing recovery: scanned up to log sequence number 1053 398798848
InnoDB: Doing recovery: scanned up to log sequence number 1053 404041728
.......

论坛徽章:
0
2 [报告]
发表于 2010-11-19 13:59 |只看该作者
我也出现过类似的状态,不知道为什么?求解

论坛徽章:
0
3 [报告]
发表于 2010-11-22 16:17 |只看该作者
回复 1# mysqlkiki


   我自己解决了, customers.name这个表的索引坏掉了。。。

论坛徽章:
1
辰龙
日期:2015-03-23 10:24:00
4 [报告]
发表于 2010-12-10 15:48 |只看该作者
我用的时候,偶尔也会出现这种情况的
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

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

清除 Cookies - ChinaUnix - Archiver - WAP - TOP