mysql Error 1067 无法启动

今天开电脑做东西，发现连不上数据库，检查发现数据库服务没有正常启动，这几天没有

修改过数据库的配置，这是怎么回事，查看mysql.log

InnoDB: Error: could not open single-table tablespace file .\mzuowen\directors.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.





2013-12-21 14:05:52 5852 [Note] Plugin 'FEDERATED' is disabled.





2013-12-21 14:05:52 5852 [Note] InnoDB: The InnoDB memory heap is disabled





2013-12-21 14:05:52 5852 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions





2013-12-21 14:05:52 5852 [Note] InnoDB: Compressed tables use zlib 1.2.3





2013-12-21 14:05:52 5852 [Note] InnoDB: Not using CPU crc32 instructions





2013-12-21 14:05:52 5852 [Note] InnoDB: Initializing buffer pool, size = 128.0M





2013-12-21 14:05:52 5852 [Note] InnoDB: Completed initialization of buffer pool





2013-12-21 14:05:52 5852 [Note] InnoDB: Highest supported file format is Barracuda.





2013-12-21 14:05:52 5852 [Note] InnoDB: The log sequence numbers 1433459747 and 1433459747 in ibdata files do not match the log sequence number 1439697423 in the ib_logfiles!





2013-12-21 14:05:52 5852 [Note] InnoDB: Database was not shutdown normally!





2013-12-21 14:05:52 5852 [Note] InnoDB: Starting crash recovery.





2013-12-21 14:05:52 5852 [Note] InnoDB: Reading tablespace information from the .ibd files...





2013-12-21 14:05:56 5852 [Note] InnoDB: Restoring possible half-written data pages 





2013-12-21 14:05:56 5852 [Note] InnoDB: from the doublewrite buffer...





InnoDB: Last MySQL binlog file position 0 116021960, file name mysql-bin.000262





2013-12-21 14:05:57 5852 [Note] InnoDB: 128 rollback segment(s) are active.





2013-12-21 14:05:57 5852 [Note] InnoDB: Waiting for purge to start





2013-12-21 14:05:57 5852 [Note] InnoDB: 5.6.11 started; log sequence number 1439697423





2013-12-21 14:06:01 5852 [Note] Server hostname (bind-address): '*'; port: 3306





2013-12-21 14:06:01 5852 [Note] IPv6 is available.





2013-12-21 14:06:01 5852 [Note]   - '::' resolves to '::';





2013-12-21 14:06:01 5852 [Note] Server socket created on IP: '::'.





2013-12-21 14:06:03 5852 [Note] Event Scheduler: Loaded 0 events





2013-12-21 14:06:03 5852 [Note] D:\web\mysql-5.6.11-winx64\bin\mysqld: ready for connections.





Version: '5.6.11-log'  socket: ''  port: 3306  MySQL Community Server (GPL)

转载请注明本文链接：http://www.simapple.com/229.html