Backup fails if DROP DATABASE executed during backup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Unassigned |
Bug Description
./xtrabackup --backup
>> log scanned up to (3 586332287)
Copying ./ibdata1
to /data/backup/
...done
Copying ./sbtest/sbtest.ibd
to /data/backup/
...done
Copying ./test/district.ibd
to /data/backup/
...done
Copying ./test/
to /data/backup/
>> 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
Changed in percona-xtrabackup: | |
importance: | Undecided → Medium |
status: | Fix Committed → Fix Released |
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 ibdata1 sbtest/ sbtest. ibd test/district. ibd order_line. ibd test/order_ line.ibd
>>> log scanned up to (3 586332287)
> Copying ./ibdata1
> to /data/backup/
> ...done
> Copying ./sbtest/sbtest.ibd
> to /data/backup/
> ...done
> Copying ./test/district.ibd
> to /data/backup/
> ...done
> Copying ./test/
> to /data/backup/
>>> 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
-- conferences. percona. com/
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://