[MDEV-22704] [ERROR] InnoDB: page [page id: space=219, page number=1590] (313 records, index id 540). Created: 2020-05-25  Updated: 2020-06-28  Resolved: 2020-06-28

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.13
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Matt Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: corruption, need_feedback
Environment:

Centos 8


 Description   

InnoDB: tuple DATA TUPLE: 3 fields;
0: len 1; hex 2a; asc *;;
1: len 4; hex 80000000; asc ;;
2: len 32; hex 3438633739643834623238353534376338313439323234376362353438653231; asc 48c79d84b285547c81492247cb548e21;;

InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
0: len 1; hex 2a; asc *;;
1: len 4; hex 80000000; asc ;;
2: len 30; hex 343839363336613633616361646164336431316264326361633832323761; asc 489636a63acadad3d11bd2cac8227a; (total 32 bytes);
2020-05-25 15:07:02 1 [ERROR] InnoDB: page [page id: space=219, page number=2392] (279 records, index id 540).
2020-05-25 15:07:02 1 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
2020-05-25 15:07:03 4 [ERROR] InnoDB: Unable to find a record to delete-mark
InnoDB: tuple DATA TUPLE: 3 fields;
0: len 1; hex 2a; asc *;;
1: len 4; hex 80000000; asc ;;
2: len 32; hex 3936633732306562366266616532643337383464333239343164393165306636; asc 96c720eb6bfae2d3784d32941d91e0f6;;

InnoDB: record PHYSICAL RECORD: n_fields 3; compact format; info bits 0
0: len 1; hex 2a; asc *;;
1: len 4; hex 80000000; asc ;;
2: len 30; hex 393662393630646564373136623331383830366434656336363832386463; asc 96b960ded716b318806d4ec66828dc; (total 32 bytes);
2020-05-25 15:07:03 4 [ERROR] InnoDB: page [page id: space=219, page number=1590] (313 records, index id 540).
2020-05-25 15:07:03 4 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

 Comments   
Comment by Thirunarayanan Balathandayuthapani [ 2020-05-26 ]

Matt.N Please attach the error log file and my.cnf file. More detail description could be useful to understand the root cause.(like when it occurs or any command or issue happening consistently). Thanks for your report

Comment by Marko Mäkelä [ 2020-05-26 ]

Matt.N, can you please provide more information, such as the complete error log, the table schema, and the configuration parameters?

The corrupted tablespace ID is 219. You should be able to identify the table via INFORMATION_SCHEMA.INNODB_SYS_TABLES or by finding a .ibd file where the bytes 34 to 37 from the start of the file contain the bytes 0x000000db (big-endian format).

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