Error (2): trying to extend a single-table tablespace 20 applying log on a compact backup

[Vadim Tkachenko]

I am playing with
lp:~akopytov/percona-xtrabackup/compact-backups

Backup was taken as
 innobackupex --compact /mnt/fio/back/ --socket=/tmp/mysql.sock

now trying to apply log:

innobackupex --apply-log --rebuild-indexes --use-memory=10G /mnt/fio/back/2012-12-11_17-30-37/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 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!".

121211 18:24:59 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/mnt/fio/back/2012-12-11_17-30-37/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/mnt/fio/back/2012-12-11_17-30-37 --use-memory=10G --rebuild-indexes

xtrabackup_55 version 2.1.0 for Percona Server 5.5.16 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /mnt/fio/back/2012-12-11_17-30-37
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(363149060710)
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:100M: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.
121211 18:24:59 InnoDB: Warning: allocated tablespace 23, old maximum was 9
Expanding ./tpccw2500/new_orders.ibd
Expanding ./tpccw2500/customer.ibd
Expanding ./tpccw2500/history.ibd
Expanding ./tpccw2500/orders.ibd
Expanding ./tpccw2500/district.ibd
Expanding ./tpccw2500/warehouse.ibd
Expanding ./tpccw2500/item.ibd
Expanding ./tpccw2500/stock.ibd
Expanding ./tpccw2500/order_line.ibd
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:100M: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 10737418240 bytes for buffer pool (set by --use-memory parameter)
121211 18:41:39 InnoDB: The InnoDB memory heap is disabled
121211 18:41:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121211 18:41:39 InnoDB: Compressed tables use zlib 1.2.3
121211 18:41:39 InnoDB: Initializing buffer pool, size = 10.0G
121211 18:41:40 InnoDB: Completed initialization of buffer pool
121211 18:41:40 InnoDB: highest supported file format is Barracuda.
121211 18:41:41 InnoDB: Waiting for the background threads to start
Rebuilding indexes for table tpccw2500/customer (space id: 20)
  Found index idx_customer
  Dropping 1 index(es).
  Rebuilding 1 index(es).
InnoDB: Error (2): trying to extend a single-table tablespace 20
InnoDB: by single page(s) though the space size 1123712. Page no 1123712.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 376.

[Stewart Smith (stewart)]

NOTE: this bug was only ever in the compact-backups branch, and before it was merged into trunk.

[Shahriyar Rzayev (rzayev-sehriyar)]

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