[MDEV-30438] innodb.undo_truncate,4k fails when --innodb-immediate-scrub-data-uncompressed is enabled Created: 2023-01-20  Updated: 2023-01-23  Resolved: 2023-01-23

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11
Fix Version/s: 10.11.2, 10.5.19, 10.6.12, 10.7.8, 10.8.7, 10.9.5, 10.10.3

Type: Bug Priority: Major
Reporter: Thirunarayanan Balathandayuthapani Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-15528 Avoid writing freed InnoDB pages Closed

 Description   

innodb.undo_truncate,4k fails when immediate scrubbing is enabled. The following error
shows up:

innodb.undo_truncate '2,32k,innodb'      [ pass ]  17120
 
innodb.undo_truncate '2,64k,innodb'      [ pass ]  16403
 
innodb.undo_truncate '16k,2,innodb'      [ pass ]  16090
 
innodb.undo_truncate '2,4k,innodb'       [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2023-01-20 15:36:55
 
line
 
2023-01-20 15:36:52 0 [ERROR] [FATAL] InnoDB: Trying to write 4096 bytes at 2621440 outside the bounds of the file: .//undo002
 
Attempting backtrace. You can use the following information to find out
 
^ Found warnings in /home/thiru/mariarepo/10.6/10.6-latest/bdebug/mysql-test/var/log/mysqld.1.err

During truncation of innodb undo log tablespace, InnoDB fails to clear the freed ranges.
During shutdown, it tries to flush the freed page ranges and does the outside of bound.

 Comments   
Comment by Thirunarayanan Balathandayuthapani [ 2023-01-20 ]

Patch is in bb-10.5-MDEV-30438

Comment by Marko Mäkelä [ 2023-01-20 ]

OK to push if you retain the assertion ut_ad(!m_freed_space).

Generated at Thu Feb 08 10:16:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.