InnoDB: Operating system error number 5 in a file operation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Expired
|
Undecided
|
Unassigned |
Bug Description
xtrabackup --backup --target_
171105 13:08:59 version_check Connecting to MySQL server with DSN 'dbi:mysql:
171105 13:08:59 version_check Connected to MySQL server
171105 13:08:59 version_check Executing a version check against the server...
171105 13:08:59 version_check Done.
171105 13:08:59 Connecting to MySQL server host: localhost, user: root, password: set, port: 3306, socket: /var/run/
Using server version 10.1.26-
xtrabackup version 2.3.9 based on MySQL server 5.6.24 Linux (x86_64) (revision id: fde0e3e)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 65536
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: using O_DIRECT
171105 13:08:59 >> log scanned up to (7596606277)
InnoDB: Retry attempts for reading partial data failed.
InnoDB: Tried to read 16384 bytes at offset 81920. Was only able to read 0.
2017-11-05 13:08:59 7fb20f617740 InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://
InnoDB: File (unknown): 'read' returned OS error 105. Cannot continue operation
2017-11-05 13:08:59 7fb20f617740 InnoDB: Assertion failure in thread 140402738952000 in file os0file.cc line 658
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
13:08:59 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
xtrabackup(
xtrabackup(
/lib/x86_
/lib/x86_
/lib/x86_
xtrabackup(
xtrabackup(
xtrabackup() [0x6c18c7]
xtrabackup() [0x58ef2c]
xtrabackup(
xtrabackup(
/lib/x86_
xtrabackup() [0x58d0c6]
Please report a bug at https:/
errno 5 means IO error. Please make sure that your FS is not corrupt. Also make sure that it support O_DIRECT.