Missing space_id from *.ibd.meta Leads to Assertion
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/
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://
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.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/
# ~ > cat /data2/
page_size = 16384
Related branches
- Alexey Kopytov (community): Approve
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 66 lines (+49/-1)2 files modifiedsrc/xtrabackup.cc (+6/-1)
test/t/bug1112224.sh (+43/-0)
- Alexey Kopytov (community): Approve
- George Ormond Lorch III: Pending (g2) requested
-
Diff: 66 lines (+49/-1)2 files modifiedsrc/xtrabackup.cc (+6/-1)
test/t/bug1112224.sh (+43/-0)
- Alexey Kopytov (community): Needs Fixing
- George Ormond Lorch III (community): Approve (g2)
-
Diff: 66 lines (+49/-1)2 files modifiedsrc/xtrabackup.cc (+6/-1)
test/t/bug1112224.sh (+43/-0)
Changed in percona-xtrabackup: | |
status: | Triaged → In Progress |
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.