MySQL Bugs: #101409: Bug in MySQL Role MySQL community 8.0.20.

Bug #101409	Bug in MySQL Role MySQL community 8.0.20.
Submitted:	31 Oct 2020 18:10	Modified:	2 Nov 2020 13:45
Reporter:	lokesh singhal	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	8.0.20	OS:	Any
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
2020-10-31T15:30:58.887397Z 3228 [ERROR] [MY-011899] [InnoDB] [FATAL] Unable to read page [page id: space=422, page number=4] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the
 table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/refman/8.0/en/ for more details. Aborting...

    
2020-10-31T15:30:58.887390Z 3228 [ERROR] [MY-011966] [InnoDB] trying to read page [page id: space=422, page number=4] in nonexisting or being-dropped tablespace

    
2020-10-31T15:30:58.887371Z 3228 [ERROR] [MY-012157] [InnoDB] Trying to do I/O to a tablespace which exists without an .ibd data file. I/O type: read, page: [page id: space=422, page number=4], I/O length: 16384 bytes

How to repeat:
Just executing query getting error again and again.

Hi,

This does not look like a MySQL bug. In order to help you recover data from corrupted table or table migrated from another system please contact either our MySQL Support team or check out free support on our forum.

all best
Bogdan