Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5, 10.6, 10.3(EOL), 10.4(EOL), 10.7(EOL), 10.8(EOL)
Description
When running mariabackup with the --rsync option backups fail starting with MariaDB 10.3 with:
rsync: link_stat "/var/lib/mysql/var/lib/mysql/ib_buffer_pool" failed: No such file or directory (2)
Note how the datadir part in the path is duplicated.
More complete output:
root@ubuntu-focal:~# mariabackup --backup --user=root --rsync
|
[00] 2022-07-15 13:23:14 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: /run/mysqld/mysqld.sock
|
[00] 2022-07-15 13:23:14 Using server version 10.5.16-MariaDB-1:10.5.16+maria~focal-log
|
mariabackup based on MariaDB server 10.5.16-MariaDB debian-linux-gnu (x86_64)
|
[...]
|
[00] 2022-07-15 13:23:15 Starting rsync as: rsync -t . --files-from=/tmp/xtrabackup_rsyncfiles_pass1 /root/xtrabackup_backupfiles/
|
rsync: link_stat "/var/lib/mysql/var/lib/mysql/ib_buffer_pool" failed: No such file or directory (2)
|
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1207) [sender=3.1.3]
|
[00] 2022-07-15 13:23:15 rsync finished successfully.
|
[00] 2022-07-15 13:23:15 Finished a prep copy of non-InnoDB tables and files
|
[00] 2022-07-15 13:23:15 Acquiring BACKUP LOCKS...
|
[00] 2022-07-15 13:23:15 Starting to backup non-InnoDB tables and files
|
[00] 2022-07-15 13:23:15 Starting rsync as: rsync -t . --files-from=/tmp/xtrabackup_rsyncfiles_pass2 /root/xtrabackup_backupfiles/
|
rsync: link_stat "/var/lib/mysql/var/lib/mysql/ib_buffer_pool" failed: No such file or directory (2)
|
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1207) [sender=3.1.3]
|
[00] 2022-07-15 13:23:15 Error: rsync failed with error code 1
|
mariabackup: Stopping log copying thread.[00] 2022-07-15 13:23:15 >> log scanned up to (55832)
|
PS: I also wonder what this option is good for anyway?
The documentation says:
During normal operation, Mariabackup transfers local
|
non-InnoDB files using a separate call to cp for each file.
|
Using this option, you can optimize this process by
|
performing this transfer with rsync, instead.
|
which does not make sense to me as there is nothing for rsync to optimize if the target directory is empty anyways, as is required by mariabackup? So rsync would just fall back to a regular cp?
Attachments
Issue Links
- is caused by
-
MDEV-27524 Incorrect binlogs after Galera SST using rsync and mariabackup
- Closed
- relates to
-
MDEV-28758 Mariabackup copies binary logs to backup directory
- Closed