MySQL Bugs: #107627: innodb_stress.innodb_bigstress_crash

Bug #107627	innodb_stress.innodb_bigstress_crash_blob test fails
Submitted:	22 Jun 2022 1:08	Modified:	22 Jun 2022 7:17
Reporter:	Manuel Ung	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S6 (Debug Builds)
Version:	8.0.29	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
innodb_stress.innodb_bigstress_crash_blob can fail with an assertion:

2022-06-22T00:56:17.075682Z 8 [ERROR] [MY-013183] [InnoDB] Assertion failure: buf0buf.cc:4163:m_mode == Page_fetch::POSSIBLY_FREED || !block->page.file_page_was_freed thread 139783611328256

How to repeat:
I was able to repro with this command on a debug build:

./mtr --mem --parallel=16 --repeat=16 innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob innodb_stress.innodb_bigstress_crash_blob

Hello Manuel Ung,

Thank you for the report and feedback.

regards,
Umesh

Hello Manuel Ung,

Thank you for the report and feedback.

regards,
Umesh

As a side note, I don't know if the assertion failure has any correctness implications for release builds.

On release builds, I sometimes see checksum failures like this instead, though I'm not sure if it's related.

CURRENT_TEST: innodb_stress.innodb_bigstress_crash_blob
mysqltest: At line 136:
In included file ./suite/innodb_stress/include/innodb_stress.inc: 140
included from /home/mung/mysql-server/mysql-test/suite/innodb_stress/t/innodb_bigstress_crash_blob.test: 37

The result from queries just before the failure was:
start slave;
Warnings:
Warning 1287    'START SLAVE' is deprecated and will be removed in a future release. Please use START REPLICA instead
Checksum slave
The checksums of table t1 for master and slave do not match for 1 th
crash. This may happen if there is a corrupt recovery log or a bug in crash
recovery. You can take a look at the logs in /home/mung/mysql-server/_build-8.0-Release/mysql-test/var/tmp/2/load_generator to see the
queries issued before the crash.