InnoDB: Assertion failure in thread <n> in file log0recv.c line 1246 InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page) == dict_table_is_comp(index->table)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
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!".
130328 01:33:00 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-
xtrabackup_55 version 2.0.6 for Percona Server 5.5.16 Linux (x86_64) (revision id: undefined)
xtrabackup: cd to /srv/mysql/data
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=95141888, start_lsn=
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: Temporary instance for recovery is set as followings.
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: innodb_
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
130328 1:33:02 InnoDB: The InnoDB memory heap is disabled
130328 1:33:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130328 1:33:02 InnoDB: Compressed tables use zlib 1.2.3
130328 1:33:02 InnoDB: Initializing buffer pool, size = 100.0M
130328 1:33:02 InnoDB: Completed initialization of buffer pool
130328 1:33:02 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 312563257050
130328 1:33:02 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 312568499712 (6 %)
InnoDB: Doing recovery: scanned up to log sequence number 312573742592 (12 %)
InnoDB: Doing recovery: scanned up to log sequence number 312578985472 (18 %)
InnoDB: Doing recovery: scanned up to log sequence number 312584228352 (24 %)
InnoDB: Doing recovery: scanned up to log sequence number 312589471232 (30 %)
130328 1:33:03 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 130328 1:36:17 InnoDB: Assertion failure in thread 140710830794496 in file log0recv.c line 1246
InnoDB: Failing assertion: !page || (ibool)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
Aborted (core dumped)
innobackupex: Error:
innobackupex: ibbackup failed at /usr//bin/
affects: | percona-server → percona-xtrabackup |
This is most likely a server problem, or to be more specific, a problem with InnoDB not being crash-safe (and thus, backup-safe) under some circumstances.
We've been getting similar reports for XtraBackup, but there are also similar reports against the server, e.g.:
http:// www.chriscalend er.com/ ?p=355 bugs.mysql. com/bug. php?id= 64429
http://
In both cases the assertion is triggered after recovering from a crash (a hardware crash in the first case, or due to another assertion failure in the second one).
I have changed the project to XtraBackup though, since the problem occurred there.
It is rather tricky to debug and fix this in either XtraBackup or server, because as I wrote, the most likely reason is crash or backup occurring at some sensitive time.
I assume you don't have a reproducible case. But some details on what the server was doing at the time when the backup was taken may be helpful to investigate it further.