mysql启动错误，提示crash 错误
:: mysqld_safe Starting mysqld daemon with databases from /data/mysql_data
-- :: [Note] Plugin 'FEDERATED' is disabled.
-- :: [Note] InnoDB: Using atomics to ref count buffer pool pages
-- :: [Note] InnoDB: The InnoDB memory heap is disabled
-- :: [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
-- :: [Note] InnoDB: Memory barrier is not used
-- :: [Note] InnoDB: Compressed tables use zlib 1.2.
-- :: [Note] InnoDB: Using CPU crc32 instructions
-- :: [Note] InnoDB: Initializing buffer pool, size = 512.0M
-- :: [Note] InnoDB: Completed initialization of buffer pool
-- :: [Note] InnoDB: Highest supported file format is Barracuda.
-- :: [Note] InnoDB: The log sequence numbers and in ibdata files do not match the log sequence number in the ib_logfiles!
-- :: [Note] InnoDB: Database was not shutdown normally!
-- :: [Note] InnoDB: Starting crash recovery.
-- :: [Note] InnoDB: Reading tablespace information from the .ibd files...
-- :: [Note] InnoDB: Restoring possible half-written data pages
-- :: [Note] InnoDB: from the doublewrite buffer...
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
-- :: 7fee6965f7e0 InnoDB: Error: page log sequence number
InnoDB: is in the future! Current system log sequence number .
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number in space ,
InnoDB: space name /data/mysql_data/ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset , len , i/o type .
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
-- :: 7fee6965f7e0 InnoDB: Assertion failure in thread in file fil0fil.cc line
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.
:: UTC - mysqld got signal ;
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. key_buffer_size=
read_buffer_size=
max_used_connections=
max_threads=
thread_count=
connection_count=
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 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 = thread_stack 0x40000
/home/wenba/mysql-latest/bin/mysqld(my_print_stacktrace+0x35)[0x8e7c25]
/home/wenba/mysql-latest/bin/mysqld(handle_fatal_signal+0x41b)[0x65582b]
/lib64/libpthread.so.(+0xf710)[0x7fee69245710]
/lib64/libc.so.(gsignal+0x35)[0x7fee6788a625]
/lib64/libc.so.(abort+0x175)[0x7fee6788be05]
/home/wenba/mysql-latest/bin/mysqld[0xa85c37]
/home/wenba/mysql-latest/bin/mysqld[0xa56e7a]
/home/wenba/mysql-latest/bin/mysqld[0xa57597]
/home/wenba/mysql-latest/bin/mysqld[0xa458b5]
/home/wenba/mysql-latest/bin/mysqld[0xa1412e]
/home/wenba/mysql-latest/bin/mysqld[0xa09416]
/home/wenba/mysql-latest/bin/mysqld[0xa097a2]
/home/wenba/mysql-latest/bin/mysqld[0xa0bb3e]
/home/wenba/mysql-latest/bin/mysqld[0x9f6605]
/home/wenba/mysql-latest/bin/mysqld[0x9458b7]
/home/wenba/mysql-latest/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x592218]
/home/wenba/mysql-latest/bin/mysqld[0x6e7646]
/home/wenba/mysql-latest/bin/mysqld(_Z11plugin_initPiPPci+0xb3e)[0x6eae7e]
/home/wenba/mysql-latest/bin/mysqld[0x585ef5]
/home/wenba/mysql-latest/bin/mysqld(_Z11mysqld_mainiPPc+0x4ec)[0x58a8dc]
/lib64/libc.so.(__libc_start_main+0xfd)[0x7fee67876d5d]
/home/wenba/mysql-latest/bin/mysqld[0x57c589]
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.
:: mysqld_safe mysqld from pid file /data/mysql_data/ooo-test.pid ended
数据文件损坏，修改my.cnf：innodb_force_recovery=6
先恢复启动，然后导出数据再重建。
http://blog.itpub.net/22664653/viewspace-1441389/
https://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
mysql启动错误，提示crash 错误的更多相关文章
- VMware ESXi 启动时提示引导错误：不是VMware引导槽。找不到管理程序(bank6 not a vmware boot bank no hypervisor found)
VMware ESXi 启动时提示引导错误: bank6 not a vmware boot bank no hypervisor found 大概中文意思是:不是VMware引导槽.找不到管理程序. ...
- 安装mysql的时候提示1045错误的解决方法
在安装mysql的时候提示1045错误,如图所示: 这种情况一般是之前卸载msyql的时候没有清理完一些文件之类的,导致给你提示存在安全问题,因此,只需要找到mysql一些系统的配置文件,并且将他们删 ...
- 编译安装或者mysql启动时遇到的错误小记
编译安装遇到的错误:进入mysql目录 [root@localhost software]# cd mysql-5.6.19 [root@localhost mysql-5.5.11]# cmake ...
- 解决mysql启动失败报1067错误
最近做项目使用 mysql 数据库 ,因为卸载了鲁大师造成了数据库文件缺失.重装mysql数据库后启动出现了1067错误,详情如下 在网上查了错误原因,将my.ini文件下的默认搜索引擎换成了 myi ...
- Mysql启动服务提示系统找不到指定的文件
Mysql启动服务: C:\Windows\system32>net start mysql发生系统错误 2. 系统找不到指定的文件. 怎么还是报这个错?难道不是由于配置的原因?对,不是由于上面 ...
- mysql免安装版1067错误终极解决办法|在windows平台下MySql启动时的1067错误的解决方法及反思
[windows事件查看] 我的电脑--此电脑--右键管理--计算机管理--系统工具--事件查看器--Windows日志--应用程序--找错误标志,如下图 [提示] 按部就班,可能并不能解决你的问题, ...
- centos 7 mysql启动失败--学会看错误日志
一.现象 mysql客户端连接时: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql ...
- oracle 11g 服务启动时提示1053错误，服务启动不了，重新配置监听解决问题
早上发现oracle服务启动不了了,找了很多资料,没找到有用的.通过重新配置监听解决问题.
- ios coredata 无任何错误提示crash
最近写程序是遇到了一种情况,对coredata 操作时,有一定几率crash,crash时无任何说明,断点调试后发现,fetch出的对象的属性竟然和数据库中的不同,不知道什么情况下导致了context ...
随机推荐
- Excel函数之rank应用
该函数的功能就是对现有数据指标进行排名 示例:对产品进行销售总额的排名 首先要知道排名需要用到rank函数 number参数就是你要进行排名的数据 ref参数就是该指标需要在哪个区域内进行比较定位排名 ...
- stm32在linux下使用clion开发
参考大神的资料,淘宝买了个板子和jlink 几个概念 jlink / openJtag,实现调试协议的硬件 openocd,这个和上面的硬件一起组成调试器 这样有个感性的认识. 具体流程 libusb ...
- C++类中this指针的理解
先要理解class的意思.class应该理解为一种类型,象int,char一样,是用户自定义的类型.用这个类型可以来声明一个变量,比如int x, myclass my等等.这样就像变量x具有int类 ...
- Github访问速度慢和下载慢的解决方法
原因 为什么访问速度慢.下载慢?github的CDN被某墙屏了,由于网络代理商的原因,所以访问下载很慢.Ping github.com 时,速度只有300多ms. 解决方法 绕过dns解析,在本地直接 ...
- SAS LOGISTIC 逻辑回归中加(EVENT='1')和不加(EVENT='1')区别
区别在于:最大似然估计分析中估计是刚好正负对调加上EVENT:%LET DVVAR = Y;%LET LOGIT_IN = S.T3;%LET LOGIT_MODEL = S.Model_Params ...
- Android 最简单的MVP案例；
随手撸个发出来: V:界面层 //界面层需要实现P.View方法,然后重写P.View中的方法:M层给的数据就在这些个方法的参数中: // 还要获取到P.Provide的实例,使用P.Provide去 ...
- Android SDK + Appium 环境搭建
一.JDK 安装 说明:JDK是包含了JAVA的运行环境(JVM+Java系统类库)和JAVA工具,所以必须最先安装. 链接: https://pan.baidu.com/s/1NfNK_K7vukF ...
- spring boot 错误处理总结
在boot 中, 对404 和 异常 有了额外的处理. 当然,我们可以定制, 如何做呢? 1 写一个继承 ErrorController 的Controller 注意, 这里一定要继承 ErrorC ...
- java编程思想（1）--对象导论
对象导论: 1.1 抽象过程 所有的语言都有抽象机制,抽象是解决复杂问题的根本方法.例如:汇编语言是对底层机器的轻微抽象.命令式语言(如:FORTRAN.BASIC.C)又是对汇编语言的抽象. jav ...
- 李清华201772020113《面向对象程序设计（Java）》第六周学习总结
第一部分 理论知识 1.继承 用已有类来构建新类的一种机制.新类可以继承父类的方法和域,同时可以在新类中添加新的方法和域. 已有类称为:超类.基类或父类.新类称作:子类.派生类或孩子类. 子类的构造器 ...