Hi Sergei,

Still having this problem with my PXDBC installation of 5.5.41-25.11-853 using Percona Xtrabackup v2.2.11-1.wheezy, but it seems that all xtrabackup/innobackupex part is doing well : 

innobackup.move.log and innobackup.prepare.log are both reporting :
150630 08:55:16  innobackupex: completed OK!

But after all this process, mysql is crashing at start :

150630  8:55:17 [Note] WSREP: SST complete, seqno: 20200769
150630  8:55:17 [Warning] Using unique option prefix myisam_recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150630  8:55:17 [Note] Plugin 'FEDERATED' is disabled.
150630  8:55:17 InnoDB: The InnoDB memory heap is disabled
150630  8:55:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150630  8:55:17 InnoDB: Compressed tables use zlib 1.2.7
150630  8:55:17 InnoDB: Using Linux native AIO
150630  8:55:17 InnoDB: Initializing buffer pool, size = 20.0G
150630  8:55:18 InnoDB: Completed initialization of buffer pool
150630  8:55:18 InnoDB: highest supported file format is Barracuda.
150630  8:55:19  InnoDB: Waiting for the background threads to start
06:55:20 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 XtraDB Cluster better by reporting any
bugs at  https://bugs.launchpad.net/percona-xtradb-cluster

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

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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7abeb9]
/usr/sbin/mysqld(handle_fatal_signal+0x372)[0x6aa6d2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7f5e078e78d0]
/usr/sbin/mysqld(_ZN3THD15raise_conditionEjPKcN11MYSQL_ERROR18enum_warning_levelES1_+0x22)[0x589062]
/usr/sbin/mysqld(_Z19push_warning_printfP3THDN11MYSQL_ERROR18enum_warning_levelEjPKcz+0xc7)[0x596d17]
/usr/sbin/mysqld(ib_warn_row_too_big+0x6d)[0x7d2d5d]
/usr/sbin/mysqld[0x869bbc]
/usr/sbin/mysqld[0x8774d3]
/usr/sbin/mysqld[0x8748cd]
/usr/sbin/mysqld[0x873a88]
/usr/sbin/mysqld[0x874e56]
/usr/sbin/mysqld[0x873a88]
/usr/sbin/mysqld[0x874e56]
/usr/sbin/mysqld[0x873a88]
/usr/sbin/mysqld[0x874e56]
/usr/sbin/mysqld[0x8753da]
/usr/sbin/mysqld[0x8e4220]
/usr/sbin/mysqld[0x8dd158]
/usr/sbin/mysqld[0x80e126]
/usr/sbin/mysqld[0x8040fc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7f5e078e00a4]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5e05b2d04d]
You may download the Percona XtraDB Cluster operations manual by visiting
http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
150630 08:55:21 mysqld_safe mysqld from pid file /var/lib/mysql/altair.pid ended

What can be done at the moment please because I'm unable to recover this node and put it up back in the cluster, this is in my opinion a high priority bug in this case ... :(

Regards,

Laurent