本文主要是介绍不要随意乱用innodb_force_recovery 参数，修复物理page 损坏，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！
##故障日志
InnoDB: End of page dump
InnoDB: Page may be an insert buffer bitmap page
2021-12-13T11:17:43.257770Z 0 [ERROR] [MY-011899] [InnoDB] [FATAL] Unable to read page [page id: space=2, page number=1] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/refman/8.0/en/ for more details. Aborting...
2021-12-13T11:17:43.257825Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:555 thread 139620632848128
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
#故障修复：
报错日志显示insert buffer bitmap page 异常，官方建议使用innodb_force_recovery 强制跳过坏块，然后mysqldump 导出数据，但是如果损坏的ibd 超过500G，你还打算用mysqldump 去导出倒入吗？
类似这种page 物理损坏，可以通过重构page 方式进行修复；
直接使用MySQL 内部 internal PPED 修复mysql page 1 ,
这篇关于不要随意乱用innodb_force_recovery 参数，修复物理page 损坏的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！
