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

InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT on mariadb-backup prepare

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 11.4.5
    • None
    • mariabackup
    • None
    • mariadb from 11.4.5-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1
      mariadb-backup based on MariaDB server 11.4.5-MariaDB Linux (x86_64)

    Description

      I have a Slave Server from which I would like to create a Backup of a subset of tables. I use the following command:

      mariadb-backup --backup --user=... --password=... --safe-slave-backup --target-dir=/bitnami/mariadb/backup --tables=application.prefix_*
      

      The Backup Step finishes without any Errors, but it seems like there is some sort of race condition, as some of the backups are invalid. I assume so, since every fourth or fifth backup fails in the following prepare step. I trigger the prepare using the following command:

      mariadb-backup --prepare --export --target-dir=/bitnami/mariadb/backup
      

      The Output is as follows:

      $ mariadb-backup --prepare --export --target-dir=/bitnami/mariadb/backuptest
      mariadb-backup based on MariaDB server 11.4.5-MariaDB Linux (x86_64)
      [00] 2025-02-28 11:27:29 mariabackup: auto-enabling --innodb-file-per-table due to the --export option
      [00] 2025-02-28 11:27:29 cd to /bitnami/mariadb/backuptest/
      [00] 2025-02-28 11:27:29 open files limit requested 0, set to 1073741816
      [00] 2025-02-28 11:27:29 This target seems to be not prepared yet.
      [00] 2025-02-28 11:27:29 mariabackup: using the following InnoDB configuration for recovery:
      [00] 2025-02-28 11:27:29 innodb_data_home_dir = .
      [00] 2025-02-28 11:27:29 innodb_data_file_path = ibdata1:12M:autoextend
      [00] 2025-02-28 11:27:29 innodb_log_group_home_dir = .
      [00] 2025-02-28 11:27:29 InnoDB: Using Linux native AIO
      [00] 2025-02-28 11:27:29 Starting InnoDB instance for recovery.
      [00] 2025-02-28 11:27:29 mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      2025-02-28 11:27:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
      2025-02-28 11:27:29 0 [Note] InnoDB: Number of transaction pools: 1
      2025-02-28 11:27:29 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      2025-02-28 11:27:30 0 [Note] InnoDB: Using Linux native AIO
      2025-02-28 11:27:30 0 [Note] InnoDB: Initializing buffer pool, total size = 100.000MiB, chunk size = 100.000MiB
      2025-02-28 11:27:30 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-02-28 11:27:30 0 [Note] InnoDB: Memory-mapped log (block size=512 bytes)
      2025-02-28 11:27:30 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=74448152457258
      2025-02-28 11:27:30 0 [Note] InnoDB: End of log at LSN=74448161922835
      2025-02-28 11:27:30 0 [ERROR] InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT for tablespace 1299
      [00] 2025-02-28 11:27:30 mariadb-backup: srv_start() returned 37 (Data structure corruption).
      

      However, using the exact same commands, some backups are valid and can be prepared correctly:

      $ mariadb-backup --prepare --export --target-dir=/bitnami/mariadb/backuptest
      mariadb-backup based on MariaDB server 11.4.5-MariaDB Linux (x86_64)
      [00] 2025-02-28 11:29:35 mariabackup: auto-enabling --innodb-file-per-table due to the --export option
      [00] 2025-02-28 11:29:35 cd to /bitnami/mariadb/backuptest/
      [00] 2025-02-28 11:29:35 open files limit requested 0, set to 1073741816
      [00] 2025-02-28 11:29:35 This target seems to be not prepared yet.
      [00] 2025-02-28 11:29:35 mariabackup: using the following InnoDB configuration for recovery:
      [00] 2025-02-28 11:29:35 innodb_data_home_dir = .
      [00] 2025-02-28 11:29:35 innodb_data_file_path = ibdata1:12M:autoextend
      [00] 2025-02-28 11:29:35 innodb_log_group_home_dir = .
      [00] 2025-02-28 11:29:35 InnoDB: Using Linux native AIO
      [00] 2025-02-28 11:29:35 Starting InnoDB instance for recovery.
      [00] 2025-02-28 11:29:35 mariabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
      2025-02-28 11:29:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
      2025-02-28 11:29:35 0 [Note] InnoDB: Number of transaction pools: 1
      2025-02-28 11:29:35 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      2025-02-28 11:29:35 0 [Note] InnoDB: Using Linux native AIO
      2025-02-28 11:29:35 0 [Note] InnoDB: Initializing buffer pool, total size = 100.000MiB, chunk size = 100.000MiB
      2025-02-28 11:29:35 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-02-28 11:29:35 0 [Note] InnoDB: Memory-mapped log (block size=512 bytes)
      2025-02-28 11:29:35 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=74448320586424
      2025-02-28 11:29:35 0 [Note] InnoDB: End of log at LSN=74448330399689
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 1298 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 162839 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 785882 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 6255447 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 6622460 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: Tablespace 6709548 was not found at './<database>/<table>.ibd', but there were no modifications either.
      2025-02-28 11:29:35 0 [Note] InnoDB: To recover: 428 pages
      2025-02-28 11:29:35 0 [Note] InnoDB: Last binlog file './mysql-bin.000543', position 533747945
      2025-02-28 11:29:35 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
      [00] 2025-02-28 11:29:35 Last binlog file ./mysql-bin.000543, position 533747945
      [00] 2025-02-28 11:29:35 mariabackup: Recovered WSREP position: ea67368c-1e60-11e7-9d0b-abd1aba3d531:5406066765 domain_id: 0
       
      [00] 2025-02-28 11:29:35 Prepare export : executing "/opt/bitnami/mariadb/bin/mariadb-backup" --mysqld --defaults-file=./backup-my.cnf --defaults-group-suffix= --datadir=. --innodb --innodb-fast-shutdown=0 --loose-partition --innodb-buffer-pool-size=104857600 --console --log-error= --skip-log-bin --bootstrap < mariabackup_prepare_for_export.sql
       
      mysqld: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb-backup' instead
      [00] 2025-02-28 11:29:36 completed OK!
      

      Current Version:

      $ mariadb --version
      mariadb from 11.4.5-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1
      $ mariadb-backup --version
      mariadb-backup based on MariaDB server 11.4.5-MariaDB Linux (x86_64)
      

      Attachments

        Issue Links

          Activity

            People

              thiru Thirunarayanan Balathandayuthapani
              tobias.bhn Tobias Bohn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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