Comment 11 for bug 1602537

170306 22:37:26 >> log scanned up to (44650360123)
170306 22:37:27 >> log scanned up to (44651559526)
170306 22:37:28 >> log scanned up to (44652487366)
2017-03-06 22:37:29 0xf37fab40 InnoDB: Assertion failure in thread 4085230400 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.
22:37:29 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
xtrabackup(my_print_stacktrace+0x33)[0x88e1ac3]
xtrabackup(handle_fatal_signal+0x262)[0x87681c2]
[0xf77a0bc0]
[0xf77a0be9]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xf71e8e1f]
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xf71ec465]
xtrabackup[0x82f24bf]
xtrabackup[0x83d8ba6]
xtrabackup[0x83d972c]
xtrabackup(_Z15xb_fil_cur_readP12xb_fil_cur_t+0x2bb)[0x83381db]
xtrabackup[0x83258d8]
xtrabackup[0x832755d]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xf7784d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xf72a9e8e]

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

I tested with PXB 2.4.6-2.precise and MySQL server 5.5.54 all 32bit binaries.