This is the error that we get with the 32bit xtrabackup binary:
Using server version 5.7.13-percona-sure1-log
/usr/bin/xtrabackup version 2.4.4 based on MySQL server 5.7.13 Linux (i686) (revision id: df58cf2)
...
160818 22:04:55 >> log scanned up to (58554133693)
160818 22:04:56 >> log scanned up to (58554133693)
160818 22:04:57 >> log scanned up to (58554133693)
2016-08-18 22:04:57 0xe6d4cb40 InnoDB: Assertion failure in thread 3872705344 in file os0file.cc line 1684
InnoDB: Failing assertion: offset > 0
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:04:57 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might 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
/usr/bin/xtrabackup(my_print_stacktrace+0x28)[0x88693c8]
/usr/bin/xtrabackup(handle_fatal_signal+0x224)[0x86735b4]
linux-gate.so.1(__kernel_sigreturn+0x0)[0xeb557410]
linux-gate.so.1(__kernel_vsyscall+0x10)[0xeb557440]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(gsignal+0x47)[0xeb119367]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x143)[0xeb11aa23]
/usr/bin/xtrabackup[0x8311d99]
/usr/bin/xtrabackup[0x8606583]
/usr/bin/xtrabackup[0x8606cdb]
/usr/bin/xtrabackup[0x8606e90]
/usr/bin/xtrabackup[0x8607036]
/usr/bin/xtrabackup(_Z17os_file_read_funcR9IORequestiPvym+0x21)[0x8607531]
/usr/bin/xtrabackup(_Z15xb_fil_cur_readP12xb_fil_cur_t+0x286)[0x83486d6]
/usr/bin/xtrabackup[0x8336fe2]
/usr/bin/xtrabackup[0x833e6c8]
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x6efb)[0xeb527efb]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e)[0xeb1d6ede]
Hello Sergei,
This is the error that we get with the 32bit xtrabackup binary:
Using server version 5.7.13- percona- sure1-log
/usr/bin/xtrabackup version 2.4.4 based on MySQL server 5.7.13 Linux (i686) (revision id: df58cf2)
... bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.7/en/ forcing- innodb- recovery. html
160818 22:04:55 >> log scanned up to (58554133693)
160818 22:04:56 >> log scanned up to (58554133693)
160818 22:04:57 >> log scanned up to (58554133693)
2016-08-18 22:04:57 0xe6d4cb40 InnoDB: Assertion failure in thread 3872705344 in file os0file.cc line 1684
InnoDB: Failing assertion: offset > 0
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.
14:04:57 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Thread pointer: 0x0 xtrabackup( my_print_ stacktrace+ 0x28)[0x88693c8 ] xtrabackup( handle_ fatal_signal+ 0x224)[ 0x86735b4] so.1(__ kernel_ sigreturn+ 0x0)[0xeb557410 ] so.1(__ kernel_ vsyscall+ 0x10)[0xeb55744 0] linux-gnu/ i686/cmov/ libc.so. 6(gsignal+ 0x47)[0xeb11936 7] linux-gnu/ i686/cmov/ libc.so. 6(abort+ 0x143)[ 0xeb11aa23] xtrabackup[ 0x8311d99] xtrabackup[ 0x8606583] xtrabackup[ 0x8606cdb] xtrabackup[ 0x8606e90] xtrabackup[ 0x8607036] xtrabackup( _Z17os_ file_read_ funcR9IORequest iPvym+0x21) [0x8607531] xtrabackup( _Z15xb_ fil_cur_ readP12xb_ fil_cur_ t+0x286) [0x83486d6] xtrabackup[ 0x8336fe2] xtrabackup[ 0x833e6c8] linux-gnu/ i686/cmov/ libpthread. so.0(+0x6efb) [0xeb527efb] linux-gnu/ i686/cmov/ libc.so. 6(clone+ 0x5e)[0xeb1d6ed e]
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
/usr/bin/
/usr/bin/
linux-gate.
linux-gate.
/lib/i386-
/lib/i386-
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/lib/i386-
/lib/i386-
Please report a bug at https:/ /bugs.launchpad .net/percona- xtrabackup