Compact backup recovery failed

Bug #1170170 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
New
Undecided
Unassigned

Bug Description

On backup of Linkbench database with partitioned table,
apply-log failed with an unclear error message.

innobackupex --apply-log --rebuild-indexes /mnt/backup/2013-04-17_20-22-53

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Ireland Ltd 2009-2012. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

IMPORTANT: Please check that the apply-log run completes successfully.
           At the end of a successful apply-log run innobackupex
           prints "completed OK!".

130417 20:31:14 innobackupex: Starting ibbackup with command: xtrabackup_56 --defaults-file="/mnt/backup/2013-04-17_20-22-53/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/mnt/backup/2013-04-17_20-22-53 --tmpdir=/tmp --rebuild-indexes

xtrabackup_56 version 2.1.0beta1 for MySQL server 5.6.10 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /mnt/backup/2013-04-17_20-22-53
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(28999835989)
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
Starting to expand compacted .ibd files.
Expanding ./linkdb/linktable#P#p2.ibd
Expanding ./linkdb/linktable#P#p15.ibd
Expanding ./linkdb/linktable#P#p9.ibd
Expanding ./linkdb/linktable#P#p4.ibd
Expanding ./linkdb/linktable#P#p12.ibd
Expanding ./linkdb/counttable.ibd
Expanding ./linkdb/linktable#P#p0.ibd
Expanding ./linkdb/nodetable.ibd
Expanding ./linkdb/linktable#P#p7.ibd
Expanding ./linkdb/linktable#P#p1.ibd
Expanding ./linkdb/linktable#P#p14.ibd
Expanding ./linkdb/linktable#P#p3.ibd
Expanding ./linkdb/linktable#P#p11.ibd
Expanding ./linkdb/linktable#P#p10.ibd
Expanding ./linkdb/linktable#P#p8.ibd
Expanding ./linkdb/linktable#P#p6.ibd
Expanding ./linkdb/linktable#P#p13.ibd
Expanding ./linkdb/linktable#P#p5.ibd
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 382.

Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

Without partitions it works fine.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

The error is not printed here possibly due to lp:1169971

Revision history for this message
Alexey Kopytov (akopytov) wrote :

Right, the error message was lost due to bug #1169971. I'll try to repeat the crash with a simple test case today.

Revision history for this message
Alexey Kopytov (akopytov) wrote :

I can reproduce the crash even without compact backups. It's just that xtrabackup_56 --prepare crashes on every partitioned table. And it wasn't caught by the test suite due to bug #1170340.

The stacktrace is identical to the one reported in bug #1169169. Closing this one as a duplicate.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.