Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34453

Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1

    XMLWordPrintable

Details

    Description

      Customer gets the following error when starting 10.6.17 immediately following sofware update from previous version, 10.6.16.

      2024-06-19 21:05:44 10 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
      		 
      2024-06-19 21:05:44 10 [ERROR] InnoDB: File './ibdata1' is corrupted
      		 
      2024-06-19 21:05:44 10 [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.
      		 
      2024-06-19 21:05:44 10 [ERROR] mariadbd: Index for table 'gtid_slave_pos' is corrupt; try to repair it
      		 
      2024-06-19 21:05:44 10 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
      		 
      2024-06-19 21:05:44 10 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
      		 
      2024-06-19 21:05:44 0x7f266c669700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/trx/trx0purge.cc line 268

      For customer, this has occurred more than one time.

      Customer discovered a workaround:
      Start database one time with 

      innodb_force_recovery=1

      Shutdown, remove innodb_force_recovery configuration.
      Start database normally.

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-27058 Buffer page descriptors are too large

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34059 Random innodb index corruption

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34873 corrupted index

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34978 MariaDB 11.4.2 crash read outside the bounds of the file: .//undo001

          • Major - Major loss of function.
          • Needs Feedback

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35056 InnoDB: Trying to read 16384 bytes at xxxx outside the bounds of the file: ./ibdata1

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-35385 Server crash after reading outside of bounds on ibdata1

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32817 在最近将版本升级到10.11.5后，针对表进行频繁的读写操作不久后，出现index for table xxxx is corrupt，随后此表tablespace xxxxxx corrupted，最后Tablespace is missing for a table，此表已完全不可用

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33922 InnoDB undo log tablespace file corruption

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34233 InnoDB crashes due to corrupted ibdata1 (Assertion failure in innodb.undo_page)

          • Major - Major loss of function.
          • Needs Feedback

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33189 Server crash after reading outside of bounds on ibdata1 , file corrupted, no auto-recovery

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              debarun Debarun Banerjee
              edward Edward Stoever
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.