Comment 2 for bug 893067

Latest 5.5.28 also crashes after the restore:

12:58:50 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346810 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x34b69f0
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 = 7f8e3102be88 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c6d05]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x696c44]
/lib/libpthread.so.0(+0xeff0)[0x7f8e30c3eff0]
/usr/sbin/mysqld[0x913216]
/usr/sbin/mysqld[0x864d20]
/usr/sbin/mysqld[0x89a79f]
/usr/sbin/mysqld[0x89e807]
/usr/sbin/mysqld[0x7f0e0b]
/usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x3e)[0x69908e]
/usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x58c)[0x61270c]
/usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0xc53)[0x55fd83]
/usr/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x485)[0x560a95]
/usr/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x48)[0x561458]
/usr/sbin/mysqld(_Z18mysqld_list_fieldsP3THDP10TABLE_LISTPKc+0x25)[0x5e6955]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xaad)[0x59bafd]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xdf)[0x638f5f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x639091]
/lib/libpthread.so.0(+0x68ca)[0x7f8e30c368ca]
/lib/libc.so.6(clone+0x6d)[0x7f8e2fed7b6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (354c0d8):
Connection ID (thread ID): 1
Status: NOT_KILLED

And I think I've found the problem. If you have innodb_import_table_from_xtrabackup=1 on the my.cnf them mysqld crashes. If you do the --copy-back and start mysqld without that parameter on my.cnf, it works perfect.

So, the restore process crashes if innodb_import_table_from_xtrabackup is enabled.