Created
May 18, 2017 18:50
-
-
Save iign/77fa2a2eafe90abe73b51c1cafd1703e to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2017-05-18 15:38:26 3914 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace minimac/accounts uses space ID: 1 at filepath: ./minimac/accounts.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: ./mysql/innodb_table_stats.ibd | |
2017-05-18 15:38:26 7fffa23f23c0 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 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment