InnoDB: Operating system error number 5 in a file operation

Bug #1730614 reported by Ari Lichtig
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Expired
Undecided
Unassigned

Bug Description

xtrabackup --backup --target_dir=/backup/mariadb_nishant5nov17 --user=root --password=test --port=3306 --host=localhost
171105 13:08:59 version_check Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_group=xtrabackup;host=localhost;port=3306;mysql_socket=/var/run/mysqld/mysqld.sock' as 'root' (using password: YES).
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/mysqld/mysqld.sock
Using server version 10.1.26-MariaDB-1~jessie
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_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
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://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
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://bugs.mysql.com.
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://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
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(my_print_stacktrace+0x2e) [0x92c6ce]
xtrabackup(handle_fatal_signal+0x261) [0x768421]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890) [0x7fb20f1f8890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fb20d2a9067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fb20d2aa448]
xtrabackup(os_file_read_func(int, void*, unsigned long, unsigned long)+0x25b) [0x7070cb]
xtrabackup(buf_dblwr_init_or_load_pages(int, char*, bool)+0x67) [0x6324f7]
xtrabackup() [0x6c18c7]
xtrabackup() [0x58ef2c]
xtrabackup(xtrabackup_backup_func()+0x9fb) [0x594e1b]
xtrabackup(main+0x8ef) [0x57c58f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fb20d295b45]
xtrabackup() [0x58d0c6]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

errno 5 means IO error. Please make sure that your FS is not corrupt. Also make sure that it support O_DIRECT.

Changed in percona-xtrabackup:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

Changed in percona-xtrabackup:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1480

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.