2023-03-29 18:06:43 5156 [Note] InnoDB: Completed initialization of buffer pool
2023-03-29 18:06:43 5156 [Note] InnoDB: Highest supported file format is Barracuda.
2023-03-29 18:06:43 5156 [Note] InnoDB: The log sequence numbers 1625977 and 1625977 in ibdata files do not match the log sequence number 1626134 in the ib_logfiles!
2023-03-29 18:06:43 5156 [Note] InnoDB: Database was not shutdown normally!
2023-03-29 18:06:43 5156 [Note] InnoDB: Starting crash recovery.
2023-03-29 18:06:43 5156 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-03-29 18:06:43 5156 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace lakala_pos_com/wp_actionscheduler_actions uses space ID: 6 at filepath: .\lakala_pos_com\wp_actionscheduler_actions.ibd. Cannot open tablespace lakala_pos_com_backup/wp_actionscheduler_actions which uses space ID: 6 at filepath: .\lakala_pos_com_backup\wp_actionscheduler_actions.ibd
InnoDB: Error: could not open single-table tablespace file .\lakala_pos_com_backup\wp_actionscheduler_actions.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. |
运维要高效，装宝塔
