It looks like the real problem was that the client connection timed out before innobackupex issued UNLOCK TABLES, but rather when copying non-InnoDB diles. It's just that the error message is misleading in such a case.
So it is essentially a duplicate of bug #408803 and will be addressed by the same patch.
It looks like the real problem was that the client connection timed out before innobackupex issued UNLOCK TABLES, but rather when copying non-InnoDB diles. It's just that the error message is misleading in such a case.
So it is essentially a duplicate of bug #408803 and will be addressed by the same patch.