innobackupex should not fail on missing files

Bug #859546 reported by Alexey Kopytov on 2011-09-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Undecided
Lachlan Mulcahy
1.6
Fix Released
Undecided
Lachlan Mulcahy
2.0
Fix Released
Undecided
Lachlan Mulcahy

Bug Description

When copying InnoDB files in stream mode, innobackupex does a special check that a file exists when tar4ibd has failed. If it doesn't, it just means the table was dropped while innobackupex was copying other files, so the error is ignored.

A similar check is required when non-InnoDB files are being copied, i.e. in backup_files(). Currently, it first takes a list of files for a database, and then iterates that list. So if a table is dropped during that process, it would fail with an error.

Related branches

Changed in percona-xtrabackup:
status: New → Confirmed

Funny. I just ran into this bug this last weekend and was about to patch it - Making some branches proposed to merge for a fix.

Basically just ignore error code 2 from tar (file not found) as non-fatal

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1129

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers