mysql 启动不了

昨天挂机插入1亿条数据，今早来mysql  就再也起不来了 。用的是wamp环境，错误日志如下：

2015-02-06 09:07:29 4884 [Note] Plugin 'FEDERATED' is disabled.
2015-02-06 09:07:29 4884 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-06 09:07:29 4884 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-06 09:07:29 4884 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-02-06 09:07:29 4884 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-02-06 09:07:29 4884 [Note] InnoDB: Not using CPU crc32 instructions
2015-02-06 09:07:29 4884 [Note] InnoDB: Initializing buffer pool, size = 512.0M
2015-02-06 09:07:29 4884 [Note] InnoDB: Completed initialization of buffer pool
2015-02-06 09:07:29 4884 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-06 09:07:29 4884 [Note] InnoDB: Log scan progressed past the checkpoint lsn 9360797708
2015-02-06 09:07:29 4884 [Note] InnoDB: Database was not shutdown normally!
2015-02-06 09:07:29 4884 [Note] InnoDB: Starting crash recovery.
2015-02-06 09:07:29 4884 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-06 09:07:29 4884 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace api/pc07_email_token uses space ID: 1 at filepath: .\api\pc07_email_token.ibd. Cannot open tablespace mysql/innodb_table_stats which uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_table_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.

好一串..... 估计是突然关机引起的。

解决方法：

再mysql ini配置文件中加：

innodb_force_recovery = 1 //强制重启mysql

然后重启wamp 稍等片刻   就会发现mysql  又活了，但是 不能执行 insert 、update、delete操作，接着再把  上面的配置删除  再重启。就真正的复活了