Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
From
http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/5412/steps/test/logs/stdio
innodb.log_data_file_size '16k,xtradb' w1 [ fail ] Found warnings/errors in server log file!
Test ended at 2017-09-16 00:13:01
line
2017-09-16 0:12:59 4080 [Warning] InnoDB: A copy of page 4:4 in the doublewrite buffer slot 13 is not within space bounds
2017-09-16 0:12:59 4080 [Warning] InnoDB: A copy of page 5:4 in the doublewrite buffer slot 19 is not within space bounds
2017-09-16 0:13:00 2392 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/ibd4f page [page id: space=5, page number=4]. You may have to recover from a backup.
2017-09-16 0:13:00 2392 [ERROR] InnoDB: Read operation failed for tablespace ./test/ibd4f.ibd offset 4 with error Page read from tablespace is corrupted.
2017-09-16 0:13:01 4080 [ERROR] Plugin 'InnoDB' init function returned error.
2017-09-16 0:13:01 4080 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
^ Found warnings in D:/win32-debug/build/mysql-test/var/1/log/mysqld.1.err
ok
Attachments
Issue Links
- duplicates
-
MDEV-12893 innodb.log_data_file_size failed in buildbot with InnoDB: Database page corruption
- Closed
- relates to
-
MDEV-12699 Improve crash recovery of corrupted data pages
- Closed