centos6.5断电重启后,MySQL启动失败 15C

161213 16:07:39 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data
2016-12-13 16:07:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-12-13 16:07:40 5243 [Note] Plugin 'FEDERATED' is disabled.
2016-12-13 16:07:40 5243 [Note] InnoDB: The InnoDB memory heap is disabled
2016-12-13 16:07:40 5243 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-12-13 16:07:40 5243 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-12-13 16:07:40 5243 [Note] InnoDB: Using Linux native AIO
2016-12-13 16:07:40 5243 [Note] InnoDB: Using CPU crc32 instructions
2016-12-13 16:07:40 5243 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-12-13 16:07:40 5243 [Note] InnoDB: Completed initialization of buffer pool
2016-12-13 16:07:40 5243 [Note] InnoDB: Highest supported file format is Barracuda.
2016-12-13 16:07:40 5243 [Note] InnoDB: Log scan progressed past the checkpoint lsn 6528157
2016-12-13 16:07:40 5243 [Note] InnoDB: Database was not shutdown normally!
2016-12-13 16:07:40 5243 [Note] InnoDB: Starting crash recovery.
2016-12-13 16:07:40 5243 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-12-13 16:07:40 5243 [Note] InnoDB: Restoring possible half-written data pages
2016-12-13 16:07:40 5243 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 6528267
2016-12-13 16:07:40 5243 [Note] InnoDB: 128 rollback segment(s) are active.
2016-12-13 16:07:40 5243 [Note] InnoDB: Waiting for purge to start
2016-12-13 16:07:40 7f161458c700 InnoDB: Assertion failure in thread 139732807370496 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:07:40 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 728082 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
161213 16:07:40 mysqld_safe mysqld from pid file /usr/local/mysql/data/mysqld.pid ended


Csdn user default icon