Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11
-
None
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.
Attachments
Issue Links
- is caused by
-
-
- Closed
-