【mysql错误】全量+增量数据校验后数据库启动报错

数据库小白一枚，正在不断学习积累知识，现将学习到的知识记录一下，也是将我的所得分享给大家！而今天这篇文章《【mysql错误】全量+增量数据校验后数据库启动报错》带大家来了解一下【mysql错误】全量+增量数据校验后数据库启动报错，希望对大家的知识积累有所帮助，从而弥补自己的不足，助力实战开发！

场景：

全量+增量数据校验后，数据库启动日志报如下错误：
（此时MySQL可以启动成功，也存在mysql进程，进入mysql查询数据可查到。重启的时候错误日志中还是会报同样的错误）

170802 21:29:31 mysqld_safe Starting mysqld daemon with databases from /data/mariadb
2017-08-02 21:29:31 139871796967424 [Note] /usr/mariadb/bin/mysqld (mysqld 10.1.24-MariaDB) starting as process 147923 ...
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: The InnoDB memory heap is disabled
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Using Linux native AIO
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Using SSE crc32 instructions
2017-08-02 21:29:31 139871796967424 [Note] InnoDB: Initializing buffer pool, size = 40.0G
2017-08-02 21:29:32 139871796967424 [Note] InnoDB: Completed initialization of buffer pool
2017-08-02 21:29:32 139871796967424 [Note] InnoDB: Highest supported file format is Barracuda.
2017-08-02 21:29:32 139871796967424 [Warning] InnoDB: The log sequence number in the ibdata files is higher than the log sequence number in the ib_logfiles! Are you sure
 you are using the right ib_logfiles to start up the database. Log sequence number in the ib_logfiles is 1086530931761, logsequence numbers stamped to ibdata file header
s are between 1087224890870 and 1087224890870.
2017-08-02 21:29:32 139871796967424 [Note] InnoDB: The log sequence numbers 1087224890870 and 1087224890870 in ibdata files do not match the log sequence number 10865309
31761 in the ib_logfiles!
2017-08-02 21:29:32 139871796967424 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2017-08-02 21:29:32 7f3670c5b800 InnoDB: Error: page 2 log sequence number 1087224745356
InnoDB: is in the future! Current system log sequence number 1086530931761.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: https://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-08-02 21:29:32 7f3670c5b800 InnoDB: Error: page 4 log sequence number 1087224626082
InnoDB: is in the future! Current system log sequence number 1086530931761.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: https://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-08-02 21:29:32 139871796967424 [Note] Server socket created on IP: '0.0.0.0'.
2017-08-02 21:29:32 139871796967424 [Note] /usr/mariadb/bin/mysqld: ready for connections.
Version: '10.1.24-MariaDB'  socket: '/tmp/mysql.sock'  port: 3306  MariaDB Server

原因：

以上就是本文的全部内容了，是否有顺利帮助你解决问题？若是能给你带来学习上的帮助，请大家多多支持golang学习网！更多关于数据库的相关知识，也可关注golang学习网公众号。