为了能快速了解并处理您的问题，请提供以下基础信息： 问题描述：重启超时 按照帖子给了权限但是还是启动不了 相关截图（日志、错误）：2024-12-02 11:26:50 3716 [Note] InnoDB: The log sequence numbers 1625977 and 1625977 in ibdata files do not match the log sequence number 68014281 in the ib_logfiles! 2024-12-02 11:26:50 3716 [Note] InnoDB: Database was not shutdown normally! 2024-12-02 11:26:50 3716 [Note] InnoDB: Starting crash recovery. 2024-12-02 11:26:50 3716 [Note] InnoDB: Reading tablespace information from the .ibd files... 2024-12-02 11:26:50 3716 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace tianmohan/emlog_attachment uses space ID: 7 at filepath: .\tianmohan\emlog_attachment.ibd. Cannot open tablespace tianmohan_backup/emlog_attachment which uses space ID: 7 at filepath: .\tianmohan_backup\emlog_attachment.ibd InnoDB: Error: could not open single-table tablespace file .\tianmohan_backup\emlog_attachment.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.
|
|
运维要高效，装宝塔
