assertion failure during apply logs of compressed backup

Bug #1003783 reported by Michael Froehlich
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

Hi,

i had a problem with a restore of a innobackupex:

i wanted to apply logs to a compressed backup and innobackupex crashed with an assertion failure:

====

Backup done with:
innobackupex --compress --slave-info --user=root --password=$PASSWORD --defaults-file=$MYCNF ${BACKUPDIR}

====

Commad:
innobackupex --apply-log 2012-05-23_00-00-08/

120524 07:58:09 innobackupex: Starting ibbackup with command: xtrabackup --prepare --target-dir=/BACKUP/STAGE/oxconfig_12-05-23-00-00-02/BACKUP/2012-05-23_00-00-08 --export

xtrabackup version 2.0.0 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: undefined)
xtrabackup: cd to /BACKUP/STAGE/oxconfig_12-05-23-00-00-02/BACKUP/2012-05-23_00-00-08
xtrabackup: Error: cannot open ./xtrabackup_checkpoints
xtrabackup: error: xtrabackup_read_metadata()
xtrabackup: This target seems not to have correct metadata...
120524 7:58:09 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
  xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=2654208, start_lsn=(1171782087)
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = ibdata1:128M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2654208
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Warning: innodb_file_io_threads is deprecated. Please use innodb_read_io_threads and innodb_write_io_threads instead
120524 7:58:09 InnoDB: Initializing buffer pool, size = 100.0M
120524 7:58:09 InnoDB: Completed initialization of buffer pool
120524 7:58:09 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1171782087
120524 7:58:09 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 1171782433 (0 %)
120524 7:58:09 InnoDB: Assertion failure in thread 140390117451520 in file fsp/fsp0fsp.c line 2954
InnoDB: Failing assertion: space != 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
innobackupex: Error:
innobackupex: ibbackup failed at /opt/MySQL-Tools/BACKUP/xtrabackup/bin/innobackupex line 371.

====

OS:
uname -a
Linux mysql-server 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux

cat /etc/issue
Debian GNU/Linux 6.0 \n \l

mysql --version
mysql Ver 14.14 Distrib 5.1.60, for unknown-linux-gnu (x86_64) using readline 5.1

innobackupex --version
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.

xtrabackup --version
xtrabackup version 2.0.0 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: undefined)

====

if i started the Backup without compression, the restore worked fine.

Thanks, Michael

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

Backups must be decompressed before applying the log. Marking as a duplicate of bug #989488.

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.