Chinaunix首页 | 论坛 | 博客
  • 博客访问: 239954
  • 博文数量: 49
  • 博客积分: 246
  • 博客等级: 二等列兵
  • 技术积分: 1034
  • 用 户 组: 普通用户
  • 注册时间: 2012-04-02 13:18
文章分类

全部博文(49)

分类: 系统运维

2014-07-25 11:03:41

朋友一次把mysql从A目录移动到B目录,结果导致innodb出错,部分文件被损坏。

error:140725 11:02:11  InnoDB: Error: page 51134 log sequence number 975290089
InnoDB: is in the future! Current system log sequence number 282944.
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.
140725 11:02:11  InnoDB: Error: page 51135 log sequence number 975322208
InnoDB: is in the future! Current system log sequence number 282944.
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.
InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.

修复:http://dev.mysql.com/doc/refman/5.0/en/forcing-innodb-recovery.html
innodb_force_recovery = 2 
mysqldump -uroot -A |gzip > mysql.$(date +%F).tar.gz
重新初始化mysql导入数据

阅读(1872) | 评论(0) | 转发(0) |
1

上一篇:python readline 读文件

下一篇:python split

给主人留下些什么吧!~~