Missing space_id from *.ibd.meta Leads to Assertion

Reported by Jervin R on 2013-02-01
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Low
Sergei Glushchenko
2.0
Low
Sergei Glushchenko
2.1
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

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.

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers