Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL)
-
None
-
kvm-bintar-quantal-amd64
Description
encryption.innodb-redo-badkey 'cbc,innodb' w4 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2017-08-17 10:04:15
|
line
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: The page [page id: space=7, page number=3] in file './test/t4.ibd' cannot be decrypted.
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: The page [page id: space=6, page number=3] in file './test/t3.ibd' cannot be decrypted.
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: Unable to decompress ./test/t2.ibd[page id: space=5, page number=3]
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t2 page [page id: space=5, page number=3]. You may have to recover from a backup.
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: Unable to decompress ./test/t1.ibd[page id: space=4, page number=3]
|
2017-08-17 10:04:12 140553760634624 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace test/t1 page [page id: space=4, page number=3]. You may have to recover from a backup.
|
^ Found warnings in /usr/local/mariadb-10.3.1-linux-x86_64/mysql-test/var/4/log/mysqld.1.err
|
|
Attachments
Issue Links
- relates to
-
MDEV-13536 DB_TRX_ID is not actually being reset when the history is removed
- Closed
-
MDEV-13542 Crashing on a corrupted page is unhelpful
- Closed