我尝试使用sudo killall -9 mysqld杀死mysql，并在innodb_force_recovery = 1中设置/tmp/my.cnf（但它已被覆盖。
我的日志说：
180108 16:03:37 mysqld_safe Logging to '/Applications/MAMP/logs/mysql_error.log'.
180108 16:03:37 mysqld_safe Starting mysqld daemon with databases from /Library/Application Support/appsolute/MAMP PRO/db/mysql56
2018-01-08 16:03:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-01-08 16:03:38 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2018-01-08 16:03:38 0 [Note] /Applications/MAMP/Library/bin/mysqld (mysqld 5.6.35) starting as process 22604 ...
2018-01-08 16:03:38 22604 [Warning] Setting lower_case_table_names=2 because file system for /Library/Application Support/appsolute/MAMP PRO/db/mysql56/ is case insensitive
2018-01-08 16:03:38 22604 [Note] Plugin 'FEDERATED' is disabled.
2018-01-08 16:03:38 22604 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-01-08 16:03:38 22604 [Note] InnoDB: The InnoDB memory heap is disabled
2018-01-08 16:03:38 22604 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-01-08 16:03:38 22604 [Note] InnoDB: Memory barrier is not used
2018-01-08 16:03:38 22604 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-01-08 16:03:38 22604 [Note] InnoDB: Using CPU crc32 instructions
2018-01-08 16:03:38 22604 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-01-08 16:03:38 22604 [Note] InnoDB: Completed initialization of buffer pool
2018-01-08 16:03:38 22604 [Note] InnoDB: Highest supported file format is Barracuda.
2018-01-08 16:03:38 22604 [Note] InnoDB: The log sequence numbers 3247503597 and 3247503597 in ibdata files do not match the log sequence number 3247503607 in the ib_logfiles!
2018-01-08 16:03:38 22604 [Note] InnoDB: Database was not shutdown normally!
2018-01-08 16:03:38 22604 [Note] InnoDB: Starting crash recovery.
2018-01-08 16:03:38 22604 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-01-08 16:03:38 22604 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mpro_pyro/applications uses space ID: 2 at filepath: ./mpro_pyro/applications.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: ./mysql/innodb_index_stats.ibd
2018-01-08 16:03:38 7fff7901e000 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_index_stats.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.
180108 16:03:38 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended