当前位置：凯发k8官方网 > 运维知识 > 数据库 >内容正文

数据库

mysql停电后无法启动不了-凯发k8官方网

发布时间：2024/10/14 数据库 32 豆豆

凯发k8官方网收集整理的这篇文章主要介绍了 mysql停电后无法启动不了_急求mysql 断电后无法启动解决方法！！！！小编觉得挺不错的,现在分享给大家,帮大家做个参考.

该楼层疑似违规已被系统折叠隐藏此楼查看此楼

rt，平台是windows xampp，断电后开机无法启动mysql。errorlog如下

2014-08-14 08:01:35 2032 [note] plugin *federated* is disabled.

2014-08-14 08:01:35 130 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.

2014-08-14 08:01:35 2032 [note] innodb: the innodb memory heap is disabled

2014-08-14 08:01:35 2032 [note] innodb: mutexes and rw_locks use windows interlocked functions

2014-08-14 08:01:35 2032 [note] innodb: compressed tables use zlib 1.2.3

2014-08-14 08:01:36 2032 [note] innodb: not using cpu crc32 instructions

2014-08-14 08:01:36 2032 [note] innodb: initializing buffer pool, size = 16.0m

2014-08-14 08:01:36 2032 [note] innodb: completed initialization of buffer pool

2014-08-14 08:01:36 2032 [note] innodb: highest supported file format is barracuda.

2014-08-14 08:01:38 2032 [note] innodb: the log sequence numbers 26455907 and 26455907 in ibdata files do not match the log sequence number 26455917 in the ib_logfiles!

2014-08-14 08:01:38 2032 [note] innodb: database was not shutdown normally!

2014-08-14 08:01:38 2032 [note] innodb: starting crash recovery.

2014-08-14 08:01:38 2032 [note] innodb: reading tablespace information from the .ibd files...

2014-08-14 08:01:39 2032 [error] innodb: attempted to open a previously opened tablespace. previous tablespace metro/line1_lable uses space id: 2 at filepath: .\metro\line1_lable.ibd. cannot open tablespace mysql/innodb_index_stats which uses space id: 2 at filepath: .\mysql\innodb_index_stats.ibd

innodb: error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.