已解决 急!mysqld启动不了,查看日志InnoDB: Error: could not open single-table tablespace file .\zentao\zt_dataset.ibd, 可以删掉zt_dataset.ibd重新启动吗?

windows一键安装禅道,使用start.exe动mysql服务失败,日志如下,请问怎么处理?

2023-06-08 13:10:37 2308 [Note] InnoDB: Completed initialization of buffer pool
2023-06-08 13:10:37 2308 [Note] InnoDB: Highest supported file format is Barracuda.
2023-06-08 13:10:37 2308 [Note] InnoDB: The log sequence numbers 2841261 and 2841261 in ibdata files do not match the log sequence number 2841441 in the ib_logfiles!
2023-06-08 13:10:37 2308 [Note] InnoDB: Database was not shutdown normally!
2023-06-08 13:10:37 2308 [Note] InnoDB: Starting crash recovery.
2023-06-08 13:10:37 2308 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-06-08 13:10:37 2308 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace zentao/zt_dataset which uses space ID: 3 at filepath: .\zentao\zt_dataset.ibd
2023-06-08 13:10:37 904  InnoDB: Operating system error number 203 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Error: could not open single-table tablespace file .\zentao\zt_dataset.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.
230608 13:10:37 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.


禅道版本 18.3 Windows安装包
操作系统 Windows Server 2008
客户端浏览器 Chrome

提问者: jcs 悬赏:20 日期: 2023-06-08 13:34:12 答案:1 点击:269

获取技术支持

QQ: 电话:
设置备注
答案列表
最佳答案
2023/06/08
您好,可以检查下磁盘还有空间吗,以及可以为这个文件分配下读写权限试试。如果还有问题,可以添加首页同事,邀请到禅道交流群,协助看下。