Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.2.32, 10.3.23, 10.4.13
-
None
Description
When MTR used with --repeat option the test fails with the following error:
mariabackup.innodb_xa_rollback 'innodb' w52 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2020-04-27 14:32:54
|
line
|
2020-04-27 14:32:03 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 1639453 is in the future! Current system log sequence number 1639445.
|
2020-04-27 14:32:03 0 [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/innodb-recovery-modes/ for information about forcing recovery.
|
2020-04-27 14:32:03 0 [ERROR] InnoDB: Page [page id: space=0, page number=311] log sequence number 1639453 is in the future! Current system log sequence number 1639445.
|
2020-04-27 14:32:03 0 [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/innodb-recovery-modes/ for information about forcing recovery.
|
^ Found warnings in /dev/shm/10.3/mysql-test/var/52/log/mysqld.1.err
|
Attachments
Issue Links
- relates to
-
MDEV-22656 Document what rollback-xa mariabackup option does
- Closed
-
MDEV-21168 Active XA transactions stop slave from working after backup was restored.
- Closed
-
MDEV-22614 "mariabackup --prepare" exits with code 0 even though innodb error is logged
- Closed