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

innodb.log_file_name fails with "Could not measure size of ..."

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.6.20, 10.11.10, 11.4.4
    • 10.6.21, 10.11.11, 11.4.5
    • Tests
    • None
    • opensuse leap 15.4, Centos 7
      compiled with BUILD/compile-pentium64-debug-max

    Description

      This is 100% repeatable on 3 systems that I tested:

      CURRENT_TEST: innodb.log_file_name
      — /home/my/maria-10.11/mysql-test/suite/innodb/r/log_file_name.result 2024-11-24 22:18:58.135077873 +0200
      +++ /home/my/maria-10.11/mysql-test/suite/innodb/r/log_file_name.reject 2024-11-26 09:58:24.713476860 +0200
      @@ -50,7 +50,7 @@
      WHERE engine = 'innodb'
      AND support IN ('YES', 'DEFAULT', 'ENABLED');
      ENGINE SUPPORT COMMENT TRANSACTIONS XA SAVEPOINTS
      -FOUND 1 /InnoDB: Could not measure the size of single-table tablespace file '.*test/t2\.ibd'/ in mysqld.1.err
      +NOT FOUND /InnoDB: Could not measure the size of single-table tablespace file '.*test/t2\.ibd'/ in mysqld.1.err

      1. restart
        SELECT * FROM INFORMATION_SCHEMA.ENGINES
        WHERE engine = 'innodb'

      Information from mysqld.1.err related to test.t2:

      024-11-26 9:58:12 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-11-26 9:58:12 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
      2024-11-26 9:58:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=60686
      2024-11-26 9:58:13 0 [Note] InnoDB: Ignoring data file './test/t2.ibd' with space ID 5. Another data file called ./test/t1.ibd exists with the same space ID.
      2024-11-26 9:58:13 0 [Note] InnoDB: End of log at LSN=67951
      2024-11-26 9:58:13 0 [ERROR] InnoDB: Cannot replay rename of tablespace 5 from './test/t1.ibd' to './test/t2.ibd' because the target file exists
      2024-11-26 9:58:13 0 [Note] InnoDB: Set innodb_force_recovery=1 to ignore corrupted pages.
      2024-11-26 9:58:13 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1480] with error Tablespace already exists

      ....
      2024-11-26 9:58:19 0 [Note] InnoDB: End of log at LSN=67951
      2024-11-26 9:58:19 0 [ERROR] InnoDB: Cannot apply log to [page id: space=5, page number=3] of corrupted file './test/t2.ibd'
      2024-11-26 9:58:19 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1480] with error Data structure corruption
      2024-11-26 9:58:19 0 [Note] InnoDB: Starting shutdown...
      2024-11-26 9:58:19 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

      ...
      024-11-26 9:58:24 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-11-26 9:58:24 0 [Note] InnoDB: File system buffers for log disabled (block s
      ize=512 bytes)
      2024-11-26 9:58:24 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=6
      0686
      2024-11-26 9:58:24 0 [Note] InnoDB: At LSN: 61789: unable to open file ./test/t3.
      ibd for tablespace 6
      2024-11-26 9:58:24 0 [Note] InnoDB: At LSN: 64627: unable to open file ./test/t1.
      ibd for tablespace 5
      2024-11-26 9:58:24 0 [Note] InnoDB: At LSN: 66550: unable to open file ./test/t2.ibd for tablespace 5
      2024-11-26 9:58:24 0 [Note] InnoDB: At LSN: 68052: unable to open file ./test/t2.ibd for tablespace 5

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              monty Michael Widenius
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.