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 ...
随机推荐
- uniDAC的安装和使用
1.解压后把UniDAC文件夹 2.在UniDAC\Source\Delphi7文件夹中找到Make.bat文件,鼠标右键“编辑”确认DELPHI7的安装路径是否正确(建议:设置成绝对路径了,防止因为 ...
- 过滤器手动注入Service Bean方法
@Override public void init(FilterConfig arg0) throws ServletException { ServletContext servletContex ...
- BottomNavigationView 使用
<?xml version="1.0" encoding="utf-8"?> <android.support.constraint.Cons ...
- Kafka介绍与消息队列
消息队列的好处: 消息队列(Message Queue) 消息: 网络中的两台计算机或者两个通讯设备之间传递的数据.例如说:文本.音乐.视频等内容. 队列:一种特殊的线性表(数据元素首尾相接),特殊之 ...
- [持续交付实践] 开篇：持续集成&持续交付综述
前言 随着微服务架构与容器虚拟化技术的发展,持续集成与持续交付的概念又重新回到了大家的视野,越来越多的公司开始使用持续集成的系统来解决频繁发布带来的质量问题:使用持续交付的工具来实现代码在不同环境上的 ...
- 注解_Annotation
---恢复内容开始--- 一.什么是注解 注解,英文Annotation,它不是程序本身,是对程序的解释,在这里我会想到为什么不能使用注释呢,因为注解是关于程序对信息的处理的流程的一些说明,而且格式也 ...
- javaee_正则表达式基础和常用表达式
正则基础: 1.1 -字符集 [ ] : 代表单个字符. [^] : 除了该字符外的所有单个字符. [a-zA-Z] : [a-z] || [A-Z]. [a-d[m-p]] :[a, d] || [ ...
- SOA和微服务的原则及对比
一.面向服务设计的原则 服务可复用:不管是否存在即时复用的机会,服务均被设计为支持潜在的可复用 服务共享一个标准契约:为了与服务提供者交互,消费者需要导入服务提供者的服务契约,这个契约可以是一个IDL ...
- leetcode152
class Solution { public: int maxProduct(vector<int>& nums) { if(nums.empty()) ; ) ]; ]; // ...
- Helm简介
什么是Helm 微服务和容器化给复杂应用部署与管理带来了极大的挑战.Helm是目前Kubernetes服务编排领域的唯一开源子项目,作为Kubernetes应用的一个包管理工具,可理解为Kuberne ...