Missing space_id from *.ibd.meta Leads to Assertion

Bug #1112224 reported by Jervin R
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Low
Sergei Glushchenko
2.0
Fix Released
Low
Sergei Glushchenko
2.1
Fix Released
Low
Sergei Glushchenko

Bug Description

The backup set was taken with 2.0.1 and using 2.0.5 to prepare.

xtrabackup: page size for /data2/MBS_BACKUPS/Restore/20130130/xxx_xxx_xxx/xxxxxx_xxx_xxx.ibd.delta is 16384 bytes
130131 22:29:43 InnoDB: Assertion failure in thread 140558481557248 in file xtrabackup.c line 5981
InnoDB: Failing assertion: space_id != ULINT_UNDEFINED
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 381.

# ~ > cat /data2/MBS_BACKUPS/Restore/failed/20130130/xxx_xxx_xxx/xxxxxx_xxx_xxx.ibd.meta
page_size = 16384

Related branches

Revision history for this message
Jervin R (revin) wrote :

I suppose this is to be invalid since some other metadata has been introduced > 2.0.1 where on 2.0.1 there was only page_size. So the workaround is to restore with the same version.

Revision history for this message
Sergei Glushchenko (sergei.glushchenko) wrote :

More likely RENAME TABLE has been performed between full and incremental backups. The only improvement we can do in this case is to print more descriptive error message before exit.

Changed in percona-xtrabackup:
status: New → Triaged
assignee: nobody → Sergei Glushchenko (sergei.glushchenko)
Changed in percona-xtrabackup:
status: Triaged → In Progress
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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.