记一次MySQL无法启动及修复经历

记得有次本地的MySQL无法启动，网上说，去删掉InnoDB日志就行，我就傻乎乎的去删掉了InnoDB相关的文件，果然，没有任何问题，正常启动了。

可是谁曾想，过了几天，故障复现了，我就按部就班的又去删除，结果，又解决了。

可是，现在棘手的问题又出现了，数据库，彻底的挂掉了。

2020-04-08 14:03:08 5506 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/dudjsf uses space ID: 146 at filepath: ./mysql/dudjsf.ibd. Cannot open tablespace mysql/ewjvuj32 which uses space ID: 146 at filepath: ./mysql/ewjvuj32.ibd
2020-04-08 14:03:08 7fccd702e740  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/ewjvuj32.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.
200408 14:03:08 mysqld_safe mysqld from pid file /usr/local/mysql/data/hostname.pid ended

按照网上的说法，没救了，因为第一次删除了InnoDB的ibdata1文件，这个文件是共享表空间，是不可以随便乱删的。

可是想着我的数据库里还存着很多东西，不能就这样放弃。

终于，找到了强力解决方法！

修复方法，打开my.cnf文件，把开启mysql的innodb强制修复属性

[mysqld]

innodb_force_recovery = 1

启动服务后，瞬间好了，数据完好无损，没有丢失。