Comment 1 for bug 337944

Percona,

How does Innodb handles it during recovery ?

If we have crash just after DROP DATABASE - the log records will
contain such records right ?

I assume we can just ignore records which correspond to non existing
tables... I also assume if table of the same name is created the
internal table ID will be different ?

Wednesday, March 4, 2009, 1:08:06 PM, you wrote:

> Public bug reported:

> ./xtrabackup --backup
>>> log scanned up to (3 586332287)
> Copying ./ibdata1
> to /data/backup/ibdata1
> ...done
> Copying ./sbtest/sbtest.ibd
> to /data/backup/sbtest/sbtest.ibd
> ...done
> Copying ./test/district.ibd
> to /data/backup/test/district.ibd
> ...done
> Copying ./test/order_line.ibd
> to /data/backup/test/order_line.ibd
>>> log scanned up to (3 586332287)
>>> log scanned up to (3 586332287)
> ...done
> 090304 13:06:38 InnoDB: Operating system error number 2 in a file operation.
> InnoDB: The error means the system cannot find the path specified.
> 090304 13:06:38 InnoDB: Fatal error: cannot open ./test/customer.ibd
> .InnoDB: Have you deleted .ibd files under a running mysqld server?

> Not sure how to handle it properly

> ** Affects: percona-xtrabackup
> Importance: Undecided
> Status: New

--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911
Attend the 2009 Percona Performance Conf
Apr 22-23 http://conferences.percona.com/