install latest version of xtrabackup run and it fails
Description
Environment
AFFECTED CS IDs
Attachments
Smart Checklist
Activity

Jira Bot March 29, 2020 at 4:15 PM
Hello ,
It's been 60 days since this issue went into Incomplete and we haven't heard
from you on this.
At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".

Jira Bot March 13, 2020 at 10:56 AM
Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.

Jira Bot February 27, 2020 at 10:56 AM
Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.

Lalit Choudhary January 29, 2020 at 10:30 AM
Hi Jim,
Let us know if this issue still exists. if yes please provide the requested data.

Sergei Glushchenko June 24, 2019 at 4:04 AM
If you mean these:
these files/sockets are fine to miss.
Since xtrabackup is getting io error from NFS, there probably should be error messages in the NFS server and/or clients logs. Are there any?
Details
Details
Assignee

Reporter

Labels
Affects versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

[mysqladm@cindnaprcpl52 ~]$ xtrabackup --backup --target-dir=/mnt/it/mysqlbackup
xtrabackup: recognized client arguments: --user=root --password=* --backup=1 --target-dir=/mnt/it/mysqlbackup
xtrabackup version 8.0.4 based on MySQL server 8.0.13 Linux (x86_64) (revision id: c2c0777)
190603 20:07:48 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup' as 'root' (using password: YES).
190603 20:07:48 version_check Connected to MySQL server
190603 20:07:48 version_check Executing a version check against the server...
190603 20:07:48 version_check Done.
190603 20:07:48 Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set
Using server version 8.0.15-5
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /home/mysqladm/mysql/data/
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = /home/mysqladm/mysql/data
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = /home/mysqladm/mysql/data
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 2147483648
Number of pools: 1
Warning: "ddcinfo.holidaylog" uses engine "MEMORY" and will not be backed up.
Warning: "lab.person" uses engine "MEMORY" and will not be backed up.
Warning: "lab.smpcomparemem" uses engine "MEMORY" and will not be backed up.
Warning: "lab.smplocusmem" uses engine "MEMORY" and will not be backed up.
Warning: "vetlab.platememory" uses engine "MEMORY" and will not be backed up.
65536 bytes should have been read. Only 512 bytes read. Retrying for the remaining bytes.
Retry attempts for reading partial data failed.
Tried to read 65536 bytes at offset 730222080, but was only able to read 512
Operating system error number 5 in a file operation.
Error number 5 means 'Input/output error'
Some operating system error numbers are described at http://dev.mysql.com/doc/refman/8.0/en/operating-system-error-codes.html
File (unknown): 'read' returned OS error 105. Cannot continue operation
Cannot continue operation.