windows本地搭建的宝塔
mysql一直正常,今天启动不了,
日志如何上传,请求帮助
2022-06-14 10:01:01 16872 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace sql_127_0_0_1/work_menu uses space ID: 6 at filepath: .\sql_127_0_0_1\work_menu.ibd. Cannot open tablespace sql_127_0_0_1_backup/work_menu which uses space ID: 6 at filepath: .\sql_127_0_0_1_backup\work_menu.ibd
InnoDB: Error: could not open single-table tablespace file .\sql_127_0_0_1_backup\work_menu.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.
|
|