"Operating system error number 22 in a file operation." while applying incremental to base backup

227 views
Skip to first unread message

Johann Tagle

unread,
Dec 21, 2019, 9:43:45 AM12/21/19
to Percona Discussion

Hello.  I'm following the steps at https://www.percona.com/doc/percona-xtrabackup/2.4/backup_scenarios/incremental_backup.html.  Am encountering a problem trying to apply the incremental to the base full backup:

# xtrabackup --prepare --apply-log-only --target-dir=/path/to/full/backup --incremental-dir=/path/to/incremental/backup

xtrabackup: [Warning] World-writable config file '/path/to/full/backup/backup-my.cnf' is ignored.
xtrabackup: recognized server arguments:
xtrabackup: [Warning] World-writable config file '/path/to/full/backup/backup-my.cnf' is ignored.
xtrabackup: recognized client arguments: --prepare=1 --apply-log-only=1 --target-dir=/path/to/full/backup --incremental-dir=/path/to/incremental/backup
xtrabackup version 2.4.18 based on MySQL server 5.7.26 Linux (x86_64) (revision id: 29b4ca5)
incremental backup from 2843182513782 is enabled.
xtrabackup: cd to /path/to/full/backup/
xtrabackup: This target seems to be already prepared with --apply-log-only.
InnoDB: Number of pools: 1
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open /path/to/incremental/backup//xtrabackup_logfile. will try to find.
  xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=63766528, start_lsn=(2843211030218)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = .
xtrabackup:   innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup:   innodb_log_group_home_dir = /path/to/incremental/backup/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 63766528
xtrabackup: [Warning] World-writable config file './backup-my.cnf' is ignored.
xtrabackup: Generating a list of tablespaces
InnoDB: Allocated tablespace ID 31712 for db_name_masked/table_name_masked, old maximum was 0
xtrabackup: page size for /path/to/incremental/backup//ibdata1.delta is 16384 bytes space id is 0
Applying /path/to/incremental/backup//ibdata1.delta to ./ibdata1...
InnoDB: Retry attempts for reading partial data failed.
InnoDB: Tried to read 16384 bytes at offset 0, but was only able to read 0
InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'
InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
InnoDB: File (unknown): 'read' returned OS error 122. Cannot continue operation
InnoDB: Cannot continue operation.

Any ideas?  Thanks!

Johann

Johann Tagle

unread,
Dec 22, 2019, 5:09:27 AM12/22/19
to Percona Discussion
It seems the problem happens when either the full backup or the incremental backup is on an nfs mounted drive, which is where we put our backups.  When I copied the backups to local disks, the application of the incremental went smoothly.
Reply all
Reply to author
Forward
0 new messages