免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
楼主: machiqiao
打印 上一主题 下一主题

紧急,mysql启动不了,请各位帮忙 [复制链接]

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2011-07-22 15:11 |显示全部楼层 |倒序浏览
本帖最后由 machiqiao 于 2011-07-22 15:12 编辑

一台rpm安装的mysql,启动不了了,数据量较大,而且没有备份,我不是很专业,真不敢动啊,望大家帮忙相助,谢谢!

日志如下:

110722 14:43:07 mysqld_safe Starting mysqld daemon with databases from /data/mysql
110722 14:43:07 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110722 14:43:08  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...
110722 14:43:09  InnoDB: Error: page 7 log sequence number 151 2702306200
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 1 log sequence number 150 2719708563
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 4 log sequence number 149 837918550
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 11 log sequence number 151 2704294980
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 5 log sequence number 151 2771374516
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 6 log sequence number 151 2770987773
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.
110722 14:43:09  InnoDB: Error: page 1785858 log sequence number 151 2770983560
InnoDB: is in the future! Current system log sequence number 131 3791365897.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
InnoDB: for more information.

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
2 [报告]
发表于 2011-07-22 16:20 |显示全部楼层
自己顶

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
3 [报告]
发表于 2011-07-22 16:40 |显示全部楼层
应该不是时间变了,这个没人去调过,可能是什么损坏引起的,现在不知道该如何恢复

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
4 [报告]
发表于 2011-07-26 15:45 |显示全部楼层

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
5 [报告]
发表于 2011-07-29 13:58 |显示全部楼层
这台服务器是朋友的,具体什么原因引起的问题我也不太清楚

---用下面这个方法试了,还是有问题,可以启动起来,但是进去select什么的,都提示和mysql失去连接
设置 my.cnf 中 innodb_force_recovery = 4,然后删除两个innodb log file,重启

论坛徽章:
2
2015年辞旧岁徽章
日期:2015-03-03 16:54:15IT运维版块每日发帖之星
日期:2015-09-11 06:20:00
6 [报告]
发表于 2011-08-08 17:14 |显示全部楼层
谢谢各位的帮忙,后面通过设置innodb_force_recovery = 3,然后一个个表导出,只有2个无关紧要的表有问题,没能正常导出,其他都没有问题,后面数据库恢复起来了。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

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

清除 Cookies - ChinaUnix - Archiver - WAP - TOP