[MDEV-16568] mariabackup.log_checksum_mismatch failed in buildbot with errors sequence number is in the future Created: 2018-06-25  Updated: 2018-06-25  Resolved: 2018-06-25

Status: Closed
Project: MariaDB Server
Component/s: Backup, Storage Engine - InnoDB, Tests
Affects Version/s: 10.2.16
Fix Version/s: 10.2.16

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16367 mariabackup: error: failed to copy en... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/9005

mariabackup.log_checksum_mismatch        w1 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2018-06-13 20:48:54
 
line
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 1665692 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 1665815 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 1665799 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=49] log sequence number 1665676 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=313] log sequence number 1665676 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 1665676 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Page [page id: space=0, page number=314] log sequence number 1665799 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:46 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:48 3948 [ERROR] InnoDB: Page [page id: space=0, page number=10] log sequence number 1665810 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:48 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:48 3948 [ERROR] InnoDB: Page [page id: space=0, page number=308] log sequence number 1665805 is in the future! Current system log sequence number 1664021.
 
2018-06-13 20:48:48 3948 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:50 6232 [ERROR] InnoDB: Page [page id: space=0, page number=307] log sequence number 1665826 is in the future! Current system log sequence number 1664031.
 
2018-06-13 20:48:50 6232 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:50 1340 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 1665820 is in the future! Current system log sequence number 1664031.
 
2018-06-13 20:48:50 1340 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Page [page id: space=7, page number=0] log sequence number 1665582 is in the future! Current system log sequence number 1664031.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Page [page id: space=7, page number=3] log sequence number 1665792 is in the future! Current system log sequence number 1664031.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Page [page id: space=7, page number=2] log sequence number 1665582 is in the future! Current system log sequence number 1664031.
 
2018-06-13 20:48:51 3324 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/xtradbinnodb-recovery-modes/ for information about forcing recovery.
 
^ Found warnings in D:/winx64-debug/build/mysql-test/var/1/log/mysqld.1.err
 
ok



 Comments   
Comment by Marko Mäkelä [ 2018-06-25 ]

Commit 23ced2f846c6a8b9b303c1365780999888fa438f, where this occurred, was between the two commits of MDEV-16367.

This problem was introduced by commit dc9c555415b1d37b713839b9f8143a053f402c0e and fixed by commit ff317fe08ea4d0e65ea421ef20786be0edf5423e, both debuting in MariaDB Server 10.2.16.

Generated at Thu Feb 08 08:29:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.