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 ...
随机推荐
- npm cnpm
npm 1.说明: npm(node package manager)是nodejs的包管理器,用于node插件管理(包括安装.卸载.管理依赖等) 2.使用npm安装插件:命令提示符执行npm ins ...
- asp.net验证码
asp.net 生成验证码问题 .添加一个.ashx文件 <%@ WebHandler Language="C#" class="CheckCode" % ...
- Linux-Shell基础(变量,字符串,数组)
一. 什么是shell shell是一个用C语言编写的程序,它是用户使用Linux的桥梁,又是一种程序设计语言. Shell 是指一种应用程序,这个应用程序提供了一个界面,用户通过这个界面访问操作系统 ...
- Xilinx------BUFG,IBUFG,BUFGP,IBUFGDS等含义以及使用
转载-----BUFG,IBUFG,BUFGP,IBUFGDS等含义以及使用 目前,大型设计一般推荐使用同步时序电路.同步时序电路基于时钟触发沿设计,对时钟的周期.占空比.延时和抖动提出了更高的要 ...
- vi 常用 文本编辑 技巧
归纳常用的Vi/Vim 文本编辑技巧,便于以后查阅. 一.把空格替换为换行 :% s/ /\r/g 二.把空行删除 :g/^$/d 三.vim以16进制打开和编辑文件 先用vim以二进制格式打开需要编 ...
- 概念吓死人的webservice
前倾提要:这是我七拼八凑,自己用手打出来的头一篇了!都是别人的想法,我抄袭的,我坦白,我这只是总结一下觉得有用的 本来题目想叫(1)REST API 和WebService(2)REST 样式和 SO ...
- Oracle 唯一 约束（unique constraint） 与 索引（index） 关系说明
一. 官网对Unique Constraints说明 http://download.oracle.com/docs/cd/E11882_01/server.112/e16508/datainte.h ...
- oracle12c安装[INS-30131]异常
接昨天写到的oracle12c安装异常解决办法. 解决这个问题百度到两种解决办法: 方法一 1.1.检查开启服务 控制面板 → 管理工具 → 服务 找到TCP/IP 和 Server 状态调为“启动” ...
- js数组条件筛选——map()
在对象数组中检索属性为指定值得某个对象使用map()就非常方便. 对象数组 var studentArray = [ {"name":"小明","ge ...
- spring 生命周期最详解
转载. https://blog.csdn.net/qq_23473123/article/details/76610052 目的 在大三开始学习spring时,老师就说spring bean周期非常 ...