- 精华
- 阅读权限
- 30
- 好友
- 相册
- 分享
- 听众
- 收听
- 注册时间
- 2023-1-28
- 在线时间
- 小时
- 最后登录
- 1970-1-1
|
发表于 2023-1-30 09:40:01
|
显示全部楼层
继续测试结果,会不会是数据库问题呢?
2023-01-30 09:20:16 6208 [Note] Plugin 'FEDERATED' is disabled.
2023-01-30 09:20:16 2648 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2023-01-30 09:20:16 6208 [Note] InnoDB: Using atomics to ref count buffer pool pages
2023-01-30 09:20:16 6208 [Note] InnoDB: The InnoDB memory heap is disabled
2023-01-30 09:20:16 6208 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-01-30 09:20:16 6208 [Note] InnoDB: Memory barrier is not used
2023-01-30 09:20:16 6208 [Note] InnoDB: Compressed tables use zlib 1.2.3
2023-01-30 09:20:16 6208 [Note] InnoDB: Not using CPU crc32 instructions
2023-01-30 09:20:16 6208 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2023-01-30 09:20:17 6208 [Note] InnoDB: Completed initialization of buffer pool
2023-01-30 09:20:17 6208 [Note] InnoDB: Highest supported file format is Barracuda.
2023-01-30 09:20:17 6208 [Note] InnoDB: The log sequence numbers 251109400 and 251109400 in ibdata files do not match the log sequence number 2207285992 in the ib_logfiles!
2023-01-30 09:20:17 6208 [Note] InnoDB: Database was not shutdown normally!
2023-01-30 09:20:17 6208 [Note] InnoDB: Starting crash recovery.
2023-01-30 09:20:17 6208 [Note] InnoDB: Reading tablespace information from the .ibd files...
2023-01-30 09:20:17 2648 InnoDB: Operating system error number 2 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[/url]
InnoDB: Error: could not open single-table tablespace file .\.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.
|
|