Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.11.3
-
Redhat Enterprise Linux 7.9
Description
We faced to index corruption in innodb table.
2024-11-20 2:04:11 4299263 [ERROR] mariadbd: Index for table 'message' is corrupt; try to repair it
|
2024-11-20 2:04:11 4299257 [ERROR] InnoDB: We detected index corruption in an InnoDB type table. You have to dump + drop + reimport the table or, in a case of widespread corruption, dump all InnoDB tables and recreate the whole tablespace. If the mariadbd server crashes after the startup or when you dump the tables. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
|
We couldn't backup table with mysqldump, but we can drop table.
So we drop table and recreate it using slave table.
Is there any cases that index was corrupted?
Do you know reason why table or index is corrupted?
And How can we prevent corruption of index?
MariaDB Server 10.11.3 was released in May 2023. Since then, there have been many bug fixes. One of them is
MDEV-32511, which was a regression due toMDEV-26827. That bug alone could explain basically any corruption. It is somewhat hard to repeat; you would need to execute mariadb-backup --backup or kill the server just at the right moment, while a log checkpoint is in progress. That is just one example; there could be other bugs that could explain this.Can you reproduce this corruption with a more recent version of MariaDB Server, such as 10.11.10?