MySQL的InnoDB数据文件损坏如何修复
发布网友
发布时间：2022-04-26 16:16
共2个回答
懂视网
时间：2022-04-08 02:29
收到短信报警，是一台R710硬盘(raid5 8块盘)坏了1块，联系机房更换硬盘， 因插槽问题 换了几块新的硬盘上去后还是亮黄灯，又将原来 1块硬盘换上后，亮绿灯，过了几分钟机器宕机了。。。。。 之后分析是主板问题，故又找了1台新的R710 将点不亮的机器上的 硬盘拔下换到新的R710上，将raid信息import后 卡在某个地方了， 发现硬盘有亮黄灯，再次更换坏的硬盘后，能进入系统了，进入系统后发现 mysql进程在，3306端口没有监听，mysql的error日志一直在输出 InnoDB: Log scan progressed past the checkpoint lsn 1613 2401579069 150613 20:34:29 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 1613 2406821888 InnoDB: Doing recovery: scanned up to log sequence number 1613 2412064768 InnoDB: Doing recovery: scanned up to log sequence number 1613 2417307648 InnoDB: Doing recovery: scanned up to log sequence number 1613 2422550528 InnoDB: Doing recovery: scanned up to log sequence number 1613 2427793408 InnoDB: Doing recovery: scanned up to log sequence number 1613 2433036288 InnoDB: Doing recovery: scanned up to log sequence number 1613 2438279168 InnoDB: Doing recovery: scanned up to log sequence number 1613 2443522048 InnoDB: Doing recovery: scanned up to log sequence number 1613 2448764928 InnoDB: Doing recovery: scanned up to log sequence number 1613 2454007808 InnoDB: Doing recovery: scanned up to log sequence number 1613 2459250688 InnoDB: Doing recovery: scanned up to log sequence number 1613 2464493568 InnoDB: Doing recovery: scanned up to log sequence number 1613 2469736448 ps aux |grep mysql root 2011 0.0 0.0 17332 1468 ? S 20:34 0:00 /bin/sh /usr/bin/mysqld_safe mysql 2042 75.9 32.0 11650168 10559232 ? Rl 20:34 15:15 /usr/sbin/mysqld --basedir=/usr --datadir=/opt/mysql --user=mysql --pid-file=/opt/mysql/1.1.1.1.pid --skip-external-locking --open-files-limit=8192 --port=3306 --socket=/var/run/mysqld/mysqld.sock netstat -tupnl |grep 3306 处理结果 待续
本文出自 “7928217” 博客，请务必保留此出处http://7938217.blog.51cto.com/7928217/1661657
mysql(innodb)故障
标签：mysql innodb
热心网友
时间：2022-04-07 23:37
执行check，repair table 都无效
alter table email_status engine =myisam; #也报错了，因为模式是innodb_force_recovery =1。
ERROR 1025 (HY000): Error on rename of '...' to '....' (errno: -1)
建立一张表：create table email_status_bak #和原表结构一样，只是把INNODB改成了MYISAM。把数据导进去insert into email_status_bak select * from email_status;
删除掉原表：
drop table email_status;
注释掉innodb_force_recovery 之后，重启。
重命名：
rename table edm_email_status_bak to email_status;
最后该回存储引擎
alter table edm_email_status engine = innodb
总结：
这里的一个重要知识点就是 对 innodb_force_recovery 参数的理解了，要是遇到数据损坏甚至是其他的损坏。可能上面的方法不行了，需要尝试另一个方法：insert into tb select * from ta limit X；甚至是mp出去，再load回来。
