Percona innobackupex not working

Bug #1506469 reported by khaled
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

When I try to backup my mysql Db via this command:innobackupex --user=root --stream=xbstream --compress --compress-threads=4 ./ > stgBackup.xbstream

its return this error:
InnoDB: Retry attempts for reading partial data failed.
InnoDB: Tried to read 1048576 bytes at offset 26952597504. Was only able to read 262144.
2015-10-15 15:49:07 7fcb37fff700 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
2015-10-15 15:49:07 7fcb37fff700 InnoDB: Assertion failure in thread 140510794610432 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.
12:49:07 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) [0x937b5e]
xtrabackup(handle_fatal_signal+0x262) [0x8f8992]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fcb42c47340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7fcb413abcc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fcb413af0d8]
xtrabackup(os_file_read_func(int, void*, unsigned long, unsigned long)+0x26b) [0x5f4ebb]
xtrabackup(xb_fil_cur_read(xb_fil_cur_t*)+0xef) [0x59dc2f]
xtrabackup() [0x595a07]
xtrabackup() [0x595cc0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182) [0x7fcb42c3f182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fcb4146f47d]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
innobackupex: got a fatal error with the following stacktrace: at /usr/bin/innobackupex line 2711.
 main::wait_for_ibbackup_file_create('/tmp/xtrabackup_suspended_2') called at /usr/bin/innobackupex line 2731
 main::wait_for_ibbackup_suspend('/tmp/xtrabackup_suspended_2') called at /usr/bin/innobackupex line 1984
 main::backup() called at /usr/bin/innobackupex line 1609
innobackupex: Error: The xtrabackup child process has died at /usr/bin/innobackupex line 2711.

Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :

Hi,

Normally, this kind of issue occurs due to disk related problems. These two lines, also indicate that in backtrace.

xtrabackup(os_file_read_func(int, void*, unsigned long, unsigned long)+0x26b) [0x5f4ebb]
xtrabackup(xb_fil_cur_read(xb_fil_cur_t*)+0xef) [0x59dc2f]

Can you check if Hard disk is okay and enough space ? i.e dmesg and df -h
I would also like to check PTDEBUG=1 output of this command. i.e

Shell> PTDEBUG=1 innobackupex --user=root --stream=xbstream --compress --compress-threads=4 ./ > stgBackup.xbstream

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-1348

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.