Comment 0 for bug 1602537

I use percona extra backup 2.4 on ubuntu 12.04 32 bit. mysql version 5.5 with multiple table space for innodb

MySql server is still up and running. just not able to do backup with innobackupex

simple command
sudo innobackupex --user=xxxx --password=xxx /Backup

and get the following error. Please check and help me

160713 02:48:57 [01] Copying ./shard1068/DB_TEXT_NEW.ibd to /home/tim/DataBk/2016-07-13_02-47-26/shard1068/DB_TEXT_NEW.ibd
160713 02:48:58 >> log scanned up to (128955499158)
160713 02:48:59 >> log scanned up to (128955499158)
160713 02:49:00 >> log scanned up to (128955499158)
160713 02:49:01 >> log scanned up to (128955499158)
160713 02:49:02 >> log scanned up to (128955499158)
160713 02:49:03 >> log scanned up to (128955499158)
160713 02:49:04 >> log scanned up to (128955499158)
160713 02:49:05 >> log scanned up to (128955499158)
160713 02:49:06 >> log scanned up to (128955499158)
160713 02:49:07 >> log scanned up to (128955499158)
160713 02:49:08 >> log scanned up to (128955499158)
160713 02:49:09 >> log scanned up to (128955499158)
160713 02:49:10 >> log scanned up to (128955499158)
160713 02:49:11 >> log scanned up to (128955499158)
160713 02:49:12 >> log scanned up to (128955499158)
160713 02:49:13 >> log scanned up to (128955499158)
160713 02:49:14 >> log scanned up to (128955499158)
160713 02:49:15 >> log scanned up to (128955499158)
160713 02:49:16 >> log scanned up to (128955499158)
160713 02:49:17 >> log scanned up to (128955499158)
160713 02:49:18 >> log scanned up to (128955499158)
160713 02:49:19 >> log scanned up to (128955499158)
160713 02:49:20 >> log scanned up to (128955499158)
160713 02:49:21 >> log scanned up to (128955499158)
160713 02:49:22 >> log scanned up to (128955499158)
160713 02:49:23 >> log scanned up to (128955499158)
160713 02:49:24 >> log scanned up to (128955499158)
160713 02:49:25 >> log scanned up to (128955499158)
160713 02:49:26 >> log scanned up to (128955499158)
160713 02:49:27 >> log scanned up to (128955499158)
160713 02:49:28 >> log scanned up to (128955499158)
160713 02:49:29 >> log scanned up to (128955499158)
160713 02:49:30 >> log scanned up to (128955499158)
160713 02:49:31 >> log scanned up to (128955499158)
160713 02:49:32 >> log scanned up to (128955499158)
160713 02:49:33 >> log scanned up to (128955499158)
160713 02:49:34 >> log scanned up to (128955499158)
160713 02:49:35 >> log scanned up to (128955499158)
160713 02:49:36 >> log scanned up to (128955499158)
160713 02:49:37 >> log scanned up to (128955499158)
160713 02:49:38 >> log scanned up to (128955499158)
160713 02:49:39 >> log scanned up to (128955499158)
160713 02:49:40 >> log scanned up to (128955499158)
160713 02:49:41 >> log scanned up to (128955499158)
160713 02:49:42 >> log scanned up to (128955499158)
160713 02:49:43 >> log scanned up to (128955499158)
160713 02:49:44 >> log scanned up to (128955499158)
160713 02:49:45 >> log scanned up to (128955499158)
160713 02:49:46 >> log scanned up to (128955499158)
160713 02:49:47 >> log scanned up to (128955499158)
160713 02:49:48 >> log scanned up to (128955499158)
160713 02:49:49 >> log scanned up to (128955499158)
160713 02:49:50 >> log scanned up to (128955499158)
160713 02:49:51 >> log scanned up to (128955500336)
160713 02:49:52 >> log scanned up to (128955500336)
160713 02:49:53 >> log scanned up to (128955500336)
160713 02:49:54 >> log scanned up to (128955500626)
160713 02:49:55 >> log scanned up to (128955500626)
160713 02:49:56 >> log scanned up to (128955500626)
160713 02:49:57 >> log scanned up to (128955500626)
160713 02:49:58 >> log scanned up to (128955500626)
160713 02:49:59 >> log scanned up to (128955500626)
160713 02:50:00 >> log scanned up to (128955500626)
160713 02:50:01 >> log scanned up to (128955500626)
160713 02:50:02 >> log scanned up to (128955500626)
160713 02:50:03 >> log scanned up to (128955500626)
160713 02:50:04 >> log scanned up to (128955500626)
160713 02:50:05 >> log scanned up to (128955500626)
160713 02:50:06 >> log scanned up to (128955500626)
160713 02:50:07 >> log scanned up to (128955500626)
160713 02:50:08 >> log scanned up to (128955500626)
160713 02:50:09 >> log scanned up to (128955500626)
160713 02:50:10 >> log scanned up to (128955500626)
160713 02:50:11 >> log scanned up to (128955500626)
160713 02:50:12 >> log scanned up to (128955500626)
160713 02:50:13 >> log scanned up to (128955500626)
160713 02:50:14 >> log scanned up to (128955500626)
160713 02:50:15 >> log scanned up to (128955500626)
160713 02:50:16 >> log scanned up to (128955500626)
160713 02:50:17 >> log scanned up to (128955500626)
160713 02:50:18 >> log scanned up to (128955500626)
160713 02:50:19 >> log scanned up to (128955500626)
160713 02:50:20 >> log scanned up to (128955500626)
160713 02:50:21 >> log scanned up to (128955500626)
160713 02:50:22 >> log scanned up to (128955500626)
160713 02:50:23 >> log scanned up to (128955500626)
160713 02:50:24 >> log scanned up to (128955500626)
160713 02:50:25 >> log scanned up to (128955500626)
160713 02:50:26 >> log scanned up to (128955500626)
160713 02:50:27 >> log scanned up to (128955500626)
160713 02:50:28 >> log scanned up to (128955500626)
160713 02:50:29 >> log scanned up to (128955500626)
160713 02:50:30 >> log scanned up to (128955500626)
160713 02:50:31 >> log scanned up to (128955500626)
160713 02:50:32 >> log scanned up to (128955500626)
160713 02:50:33 >> log scanned up to (128955500626)
160713 02:50:34 >> log scanned up to (128955500626)
160713 02:50:35 >> log scanned up to (128955500626)
160713 02:50:36 >> log scanned up to (128955500626)
160713 02:50:37 >> log scanned up to (128955500626)
160713 02:50:38 >> log scanned up to (128955500626)
160713 02:50:39 >> log scanned up to (128955500626)
160713 02:50:40 >> log scanned up to (128955500626)
160713 02:50:41 >> log scanned up to (128955500626)
160713 02:50:42 >> log scanned up to (128955500626)
160713 02:50:43 >> log scanned up to (128955500626)
2016-07-13 02:50:44 0x908fab40 InnoDB: Assertion failure in thread 2425334592 in file os0file.cc line 1639
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.
06:50:44 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
innobackupex(my_print_stacktrace+0x33)[0x881efd3]
innobackupex(handle_fatal_signal+0x262)[0x87b4d92]
[0xb76f3400]
[0xb76f3424]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb73371df]
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb733a825]
innobackupex[0x82f9f0f]
innobackupex[0x85120f8]
innobackupex[0x8512ccc]
innobackupex(_Z15xb_fil_cur_readP12xb_fil_cur_t+0x2bb)[0x833192b]
innobackupex[0x8321978]
innobackupex[0x832574d]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb76ccd4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb73f8bae]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
tim@DB04-VM:~$ innobackupex(my_print_stacktrace+0x33)[0x881efd3]
-bash: syntax error near unexpected token `my_print_stacktrace+0x33'