InnoDB: New log files created, LSN=186651663 InnoDB: Highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 186652172 InnoDB: Doing recovery: scanned up to log sequence number 186652181 (0%) InnoDB: Doing recovery: scanned up to log sequence number 186652181 (0%) InnoDB: Database was not shutdown normally! InnoDB: Starting crash recovery. InnoDB: xtrabackup: Last MySQL binlog file position 3212, file name production-bin.000001 InnoDB: Removed temporary tablespace data file: "ibtmp1" InnoDB: Creating shared tablespace for temporary tables InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... InnoDB: File './ibtmp1' size is now 12 MB. InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active. InnoDB: 32 non-redo rollback segment(s) are active. InnoDB: Waiting for purge to start InnoDB: page_cleaner: 1000ms intended loop took 10267ms. The settings
might not be optimal. (flushed=0 and evicted=0, during the time.) InnoDB: 5.7.11 started; log sequence number 186652181 xtrabackup: starting shutdown with innodb_fast_shutdown = 1 InnoDB: FTS optimize thread exiting. InnoDB: Starting shutdown... InnoDB: Shutdown completed; log sequence number 186652200 160721 23:40:39 completed OK!
xtrabackup: innodb_log_files_in_group = 2 xtrabackup: innodb_log_file_size = 50331648 xtrabackup: using the following InnoDB configuration for recovery: xtrabackup: innodb_data_home_dir = . xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend xtrabackup: innodb_log_group_home_dir = . xtrabackup: innodb_log_files_in_group = 2 xtrabackup: innodb_log_file_size = 50331648 xtrabackup: Starting InnoDB instance for recovery. xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter) InnoDB: PUNCH HOLE support not available InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Uses event mutexes InnoDB: GCC builtin __sync_synchronize() is used for memory barrier InnoDB: Compressed tables use zlib 1.2.3 InnoDB: Number of pools: 1 InnoDB: Using CPU crc32 instructions InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M InnoDB: Completed initialization of buffer pool InnoDB: page_cleaner coordinator priority: -20 InnoDB: Highest supported file format is Barracuda. InnoDB: xtrabackup: Last MySQL binlog file position 3212, file name production-bin.000001
xtrabackup: starting shutdown with innodb_fast_shutdown = 1 InnoDB: Starting shutdown... InnoDB: Shutdown completed; log sequence number 186652247 InnoDB: Number of pools: 1 160722 01:13:30 completed OK!
InnoDB: File './ibtmp1' size is now 12 MB. InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active. InnoDB: 32 non-redo rollback segment(s) are active. InnoDB: Waiting for purge to start InnoDB: Page [page id: space=0, page number=9] log sequence number
186659641 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: Page [page id: space=0, page number=10] log sequence number
186659944 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: Page [page id: space=0, page number=12] log sequence number
186662606 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: Page [page id: space=13, page number=3] log sequence number
186669950 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: 5.7.11 started; log sequence number 186652247 InnoDB: Page [page id: space=82, page number=0] log sequence number
186655532 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: Page [page id: space=83, page number=0] log sequence number
186663700 is in the future! Current system log sequence number
186652266. InnoDB:
Your database may be corrupt or you may have copied the InnoDB
tablespace but not the InnoDB log files. Please refer to
http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for
information about forcing recovery. InnoDB: xtrabackup: Last MySQL binlog file position 1421, file name production-bin.000001
xtrabackup: error: The transaction log file is corrupted. xtrabackup: error: The log was not applied to the intended LSN! xtrabackup: Log applied to lsn 186652247 xtrabackup: The intended lsn is 186672619
-停止数据库,并删除数据文件下面的所有文件 [root@localhost 20160722]# cd /var/lib/mysql [root@localhost mysql]# rm -rf *