Apply log on partial backup is giving table space errors
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.4 |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I'm using innobackupex 2.4.3 to backup some selected tables from a Percona Server 5.7.11-4-1.wheezy server running on Debian Wheezy. We have innodb-
When applying the log its crashes with reports about tables that are not included in the backup (and not in the backup directory). Please find output here:
InnoDB: xtrabackup: Last MySQL binlog file position 138024332, file name mysql-bin.111408
InnoDB: Creating shared tablespace for temporary tables
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
InnoDB: File './ibtmp1' size is now 12 MB.
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
InnoDB: 32 non-redo rollback segment(s) are active.
InnoDB: 5.7.11 started; log sequence number 43935355195374
InnoDB: page_cleaner: 1000ms intended loop took 55452ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
InnoDB: Failed to find tablespace for table `[database_
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Cannot open datafile for read-only: './[database_
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Could not find a valid tablespace file for `[database_
InnoDB: Failed to find tablespace for table `[database_
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Cannot open datafile for read-only: './[database_
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Could not find a valid tablespace file for `[database_
09:46:02 UTC - xtrabackup got signal 11 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
innobackupex(
innobackupex(
/lib/x86_
innobackupex(
innobackupex(
innobackupex(
innobackupex(
innobackupex(
innobackupex[
innobackupex(
innobackupex(
innobackupex(
innobackupex(
innobackupex(
innobackupex(
innobackupex(
/lib/x86_
/lib/x86_
[database_
I tried to also define the tables using --database when applying the log, but that doesn't help.
Changed in percona-xtrabackup: | |
status: | Expired → New |
Can you please show us the exact commands used for the backup along with MySQL server my.cnf file contents so we can replicate it to investigate.