Comment 1 for bug 713799

The race leads to an InnoDB assertion failure when a table is dropped during XtraBackup run.

Symptoms:

110206 12:25:09 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
110206 12:25:09 InnoDB: Fatal error: cannot open ./test/test.ibd
.InnoDB: Have you deleted .ibd files under a running mysqld server?
110206 12:25:09 InnoDB: Assertion failure in thread 46984453581056 in file fil/fil0fil.c line 669
InnoDB: Failing assertion: 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.1/en/forcing-recovery.html
InnoDB: about forcing recovery.
innobackupex-1.5.1: Error: ibbackup child process has died at /usr/bin/innobackupex-1.5.1 line 534.