[MDEV-23979] Corrupted page breaks recovery in innodb_gis.types Created: 2020-10-19  Updated: 2020-10-19

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5
Fix Version/s: 10.5

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Thirunarayanan Balathandayuthapani
Resolution: Unresolved Votes: 0
Labels: corruption, recovery

Issue Links:
Relates
relates to MDEV-22512 innodb_zip.recover, innodb_gis.types ... Closed

 Description   

The following failure of the test innodb_gis.types occurred on kvm-deb-sid-x86:

10.5 ee61c8c0b762840ab5badaa9d6b3a24b1c2ee8c7

2020-08-21 18:06:15 0 [Note] InnoDB: VALID: space:5163 page_no:1 page_size:16384
2020-08-21 18:06:15 0 [Note] InnoDB: Page size: 16384. Possible space_id count:1
2020-08-21 18:06:15 0 [Note] InnoDB: space_id:5163, Number of pages matched: 1/1 (16384)
2020-08-21 18:06:15 0 [Note] InnoDB: Chosen space:5163
2020-08-21 18:06:15 0 [ERROR] InnoDB: Corrupted page [page id: space=5163, page number=0] of datafile './test/t_wl6455.ibd' could not be found in the doublewrite buffer.
2020-08-21 18:06:15 0 [ERROR] InnoDB: Tablespace 5163 was not found at ./test/t_wl6455.ibd.
2020-08-21 18:06:15 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore this and to permanently lose all changes to the tablespace.
2020-08-21 18:06:15 0 [ERROR] InnoDB: Plugin initialization aborted with error Tablespace not found

This caused the test failure as follows:

10.5 ee61c8c0b762840ab5badaa9d6b3a24b1c2ee8c7

innodb_gis.types 'innodb'                w4 [ fail ]
        Test ended at 2020-08-21 18:06:16
 
CURRENT_TEST: innodb_gis.types
mysqltest: At line 76: query 'SELECT ST_AsText(g) FROM t_wl6455' failed: 1286: Unknown storage engine 'InnoDB'

Note: This differs from MDEV-22512 in that we no longer run out of the buffer pool during recovery, probably thanks to MDEV-21351. Before 10.5, we would be much more likely to hit MDEV-22512. So, this bug may in fact affect earlier versions than 10.5.


Generated at Thu Feb 08 09:26:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.