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

mariabackup --prepare --export fails if innodb_undo_directory is set and original mariadb is running

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.5.11
    • Fix Version/s: None
    • Component/s: Backup
    • Labels:
      None

      Description

      Hello,

      executing "mariabackup --prepare --export" on a server with the original mariadb server process running fails if innodb_undo_directory is set (to an absolute path) as the newly started process cannot get the lock on the undo files.

      How to reproduce:

      • set innodb_undo_tablespaces to 3 (this is probably irrelevant)
      • set innodb_undo_directory to an absolute path and restart mariadb
      • create a backup with "mariabackup --backup --defaults-file=<path_to_original_my.cnf>"
      • run "mariabackup --prepare --export"

      In the log file (*.err) you will find some errors:

      [ERROR] InnoDB: Unable to lock <innodb_undo_directory>/undo001 error: 11

      The reason is that innodb_undo_directory is set in backup-my.cnf to the same path as for the original server.
      If you comment out or delete innodb_undo_directory from backup-my.cnf, running mariabackup with export works fine.

      So the fix would be not to include innodb_undo_directory in backup-my.cnf during backup.

      Cheers
      Volker

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            vklasen Volker Klasen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration