Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Duplicate
    • 11.4.2
    • N/A
    • None

    Description

      2024-07-16 7:32:15 7 [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 InnoD
      B 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-mod
      es/ for information about forcing recovery.
      2024-07-16 7:32:15 7 [ERROR] mariadbd: Index for table 'total_main_log' is corrupt; try to repair it
      2024-07-16 7:32:15 7 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table prol2.total_main_log; Index for table 'total_main_log' is corrupt; try to repair it, Error_
      code: 1034; handler error HA_ERR_CRASHED; the event's master log mysql-bin.000834, end_log_pos 0, Gtid 0-2-1062387710, Internal MariaDB error code: 1034
      2024-07-16 07:32:15 0x7f4682d08700 InnoDB: Assertion failure in file /home/buildbot/amd64-rhel-8-rpm-autobake/build/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/storage/innobase/page/page0
      zip.cc line 4291
      InnoDB: Failing assertion: slot_rec
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mariadbd startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      240716 7:32:15 [ERROR] mysqld got signal 6 ; Sorry, we probably made a mistake, and this is a bug.

      Attachments

        Issue Links

          Activity

            alice Alice Sherepa added a comment -

            Could you please add the output SHOW CREATE TABLE? There is a bug MDEV-34357, that might be the same problem

            alice Alice Sherepa added a comment - Could you please add the output SHOW CREATE TABLE? There is a bug MDEV-34357 , that might be the same problem
            Rylov Michael added a comment -

            MariaDB [(none)]> SHOW CREATE TABLE prol2.total_log_main_log\G;

                                                                • 1. row ***************************
                                                                  Table: total_log_main_log
                                                                  Create Table: CREATE TABLE `total_log_main_log` (
                                                                  `ID` bigint(20) NOT NULL COMMENT 'total_log record ID',
                                                                  `main_ID` bigint(20) NOT NULL COMMENT 'main log record ID',
                                                                  KEY `ID` (`ID`),
                                                                  KEY `main_ID` (`main_ID`),
                                                                  CONSTRAINT `total_log_main_log_ibfk_1` FOREIGN KEY (`ID`) REFERENCES `total_log` (`ID`),
                                                                  CONSTRAINT `total_log_main_log_ibfk_2` FOREIGN KEY (`main_ID`) REFERENCES `total_log_main` (`ID`)
                                                                  ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=4 COMMENT='relation log records with main log record, one to many'
                                                                  1 row in set (0.000 sec)
            Rylov Michael added a comment - MariaDB [(none)] > SHOW CREATE TABLE prol2.total_log_main_log\G; 1. row *************************** Table: total_log_main_log Create Table: CREATE TABLE `total_log_main_log` ( `ID` bigint(20) NOT NULL COMMENT 'total_log record ID', `main_ID` bigint(20) NOT NULL COMMENT 'main log record ID', KEY `ID` (`ID`), KEY `main_ID` (`main_ID`), CONSTRAINT `total_log_main_log_ibfk_1` FOREIGN KEY (`ID`) REFERENCES `total_log` (`ID`), CONSTRAINT `total_log_main_log_ibfk_2` FOREIGN KEY (`main_ID`) REFERENCES `total_log_main` (`ID`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=4 COMMENT='relation log records with main log record, one to many' 1 row in set (0.000 sec)
            danblack Daniel Black added a comment -

            With ROW_FORMAT=COMPRESSED its looking like the same bug MDEV-34357. The assertion is on the same line (accounting for minor version differences).

            In the mean time, recommending avoiding the bug by not using ROW_FORMAT=COMPRESSED.

            danblack Daniel Black added a comment - With ROW_FORMAT=COMPRESSED its looking like the same bug MDEV-34357 . The assertion is on the same line (accounting for minor version differences). In the mean time, recommending avoiding the bug by not using ROW_FORMAT=COMPRESSED.

            People

              Unassigned Unassigned
              Rylov Michael
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.