mariaDB的innodb恢复报错解决

报错信息：

InnoDB: Doing recovery: scanned up to log sequence number 78431090263

InnoDB: 1 transaction(s) which must be rolled back or cleaned up

InnoDB: in total 0 row operations to undo

InnoDB: Trx id counter is 322491392

2017-03-02  9:03:24 140716572358688 [Note] InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percent: 0 1 2017-03-02 09:03:24 7ffa6ddfc700  InnoDB: Assertion failure in thread 140713561933568 in file log0recv.cc line 1194

InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)

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.

170302  9:03:24 [ERROR] 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.

 

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

 

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.

解决方案：

my.cnf配置：innodb_force_recovery = 6

 

转载于:https://www.cnblogs.com/bury12/p/6488824.html