一、問題日誌
2017-08-31 14:18:05 4122 [Note] InnoDB: Database was not shutdown normally! 2017-08-31 14:18:05 4122 [Note] InnoDB: Starting crash recovery. 2017-08-31 14:18:05 4122 [Note] InnoDB: Reading tablespace information from the .ibd files... 2017-08-31 14:18:05 4122 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dev/tb_test uses spac e ID: 1 at filepath: ./dev/tb_test.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/ innodb_table_stats.ibd 2017-08-31 14:18:05 2ad861898590 InnoDB: Operating system error number 2 in a file operation. InnoDB: The error means the system cannot find the path specified. InnoDB: If you are installing InnoDB, remember that you must create InnoDB: directories yourself, InnoDB does not create them. InnoDB: Error: could not open single-table tablespace file ./mysql/innodb_table_stats.ibd InnoDB: We do not continue the crash recovery, because the table may becomeInnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. 150126 14:18:06 mysqld_safe mysqld from pid file /home/mysql/mysql_app/dbdata/liuyazhuang136.pid ended
在[mysqld]群組中加入：
innodb_force_recovery=6
innodb_force_recovery參數解釋：
innodb_force_recovery影響整個InnoDB儲存引擎的復原狀況，預設值為0，表示當需要復原時執行所有的復原作業。
當無法進行有效的復原操作時，mysql有可能無法啟動，並記錄下錯誤日誌。
innodb_force_recovery可以設定為1-6,大的數字包含前面所有數字的影響。
當設定參數值大於0後，可以對錶進行select,create,drop操作,但insert,update或delete這類操作是不允許的。
1(SRV_FORCE_IGNORE_CORRUPT):忽略檢查到的corrupt頁
2(SRV_FORCE_NO_BACKGROUND):阻止主執行緒的運行，如主執行緒需要執行full purge操作，會導致crash
3(SRV_FORCE_NO_TRX_UNDO)事務回滾操作。
4(SRV_FORCE_NO_IBUF_MERGE):不執行插入緩衝的合併操作。
5(SRV_FORCE_NO_UNDO_LOG_SCAN):不查看重做日誌，InnoDB儲存引擎會將未提交的交易視為已提交。
6(SRV_FORCE_NO_LOG_REDO):不執行前滾的操作。
$mysqldump -h 192.168.209.136 -uroot -p dev > /home/mysql/dev.sql
$mysql -h 192.168.209.136 -uroot -p mysql> drop database dev; ERROR 1051 (42S02): Unknown table 'dev.tb_test'
物理刪除tb_test對應的frm和ibd檔案
mysql> drop database dev; Query OK, 0 rows affected (0.00 sec)
mysql> create database dev; Query OK, 1 row affected (0.03 sec)
5.去掉參數innodb_force_recovery
將先前設定的參數去掉後，重新啟動資料庫
##innodb_force_recovery=6
[mysql@liuyazhuang136 dev]$ mysql -h 192.168.209.136 -uroot -pmysql dev</home/mysql/dev.sql Warning: Using a password on the command line interface can be insecure. ERROR 1050 (42S01) at line 25: Table '`dev`.`tb_test`' already exists
提示表已經存在，這是因為將innodb_force_recovery參數去掉後，資料庫會進行回滾操作，會產生相應的ibd文件，所有需要將該文件刪除掉.
刪除後重新導入
[mysql@liuyazhuang136 dev]$ mysql -h 192.168.209.136 -uroot -pmysql dev</home/mysql/dev.sql
以上是MySQL表資料檔損壞導致資料庫無法啟動詳解的詳細內容。更多資訊請關注PHP中文網其他相關文章！
