Bug #115766 Database page corruption on disk or a failed file read of page
Submitted: 5 Aug 8:36 Modified: 9 Aug 15:46
Reporter: Benoit Tigeot Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.0.35 OS:Linux (RDS)
Assigned to: CPU Architecture:Any

[5 Aug 8:36] Benoit Tigeot 
Description:
Hello

We are running purge script on old data but yesterday we saw crashes on some of the resources.

Here is some informations attached

We looked at `8.0.37`, 38, 39 changelog but didn't find something that could help us. 

How to repeat:
Because it's a disk corruption we do not know how to reproduce this issue.
[5 Aug 8:36] Benoit Tigeot 
dump

Attachment: dump.txt (text/plain), 10.72 KiB.
[5 Aug 9:11] Benoit Tigeot 
It seems it's related to index, when I see in stacktrace `btr_cur_search_to_nth_level` https://github.com/mysql/mysql-server/blob/19feac3674e2ae254b3e7fa7e116fc64ac284d8d/storag...
[5 Aug 9:48] MySQL Verification Team 
Salut Monsieur Tigeot,

Thank you for your bug report.

However, let us inform you that this is a forum intended only for the bugs with fully repeatable test cases.

We have not received such a test case.

This forum operates in a manner that we try to reproduce the test case provided. If we manage to repeat it with our latest  official binaries, then we can analyse whether it is a bug or not.

Hence, we can not proceed with your report.

Can't repeat.
[9 Aug 15:46] Benoit Tigeot 
It was not related to the index but to specific row. We ran big count(*) on small range to identify those raws and see how much we were impacted.

RDS can change your innodb recovery if you ask them. If you want to perform a mysqldump after.
[12 Aug 9:33] MySQL Verification Team 
Salut Monsieur Tigeot,

Thank you for your bug report.

However, let us inform you that this is a forum intended only for the
bugs with fully repeatable test cases.

We have not received such a test case.

This forum operates in a manner that we try to reproduce the test case
provided. If we manage to repeat it with our latest  official binaries,
then we can analyse whether it is a bug or not.

Hence, we can not proceed with your report.

Can't repeat.