[網站筆記]人生很難，特別是MySQL跑不動。差點就升天了

  
要達到這張圖，我真的駛出洪荒之力了啊，E04

MySQL跑不動的原因很多。

這裡就不多贅述了，我花了一天跟這玩意兒奮鬥，終於跑出一個我看得懂的系統解釋，解決掉我的麻煩，少挨了一頓罵。

以下是MySQLy的 Logs跑出的一段人類可理解的話:

 InnoDB: Error: could not open single-table tablespace file .\tua@002djm\@0023__session.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: 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.

真心誠意地告訴各位，如果可以的話，請想盡辦法看懂logs裡的內容，真的是浮木。
我遇到的問題剛好是屬於 2) If the table is not needed, or you can restore it from a backup,then you can remove the .ibd file, and InnoDB will do a normal crash recovery and ignore that table.
所以參照第一行所說的:

 Error: could not open single-table tablespace file .\tua@002djm\@0023__session.ibd

找到出問題的檔案，然後快樂的刪除掉之後，我的XAMPP就復活了，我的老天爺~~~