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

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.

请问大家是否也有类似情况发生？我这个有时候即使正常关机都出现这个问题，只能删了数据重新建库解决