Fix for bug #932623 does not take separate doublewrite tablespace into account

Bug #1066843 reported by Alexey Kopytov
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Critical
Sergei Glushchenko
2.0
Fix Released
Critical
Sergei Glushchenko
2.1
Fix Released
Critical
Sergei Glushchenko

Bug Description

The fix for bug #932623 does not take separate doublewrite tablespace into account. The following assertion assumes the system tablespace to always have id 0:

 ut_a(dbname != NULL || space_id == 0 || space_id == ULINT_UNDEFINED);

However, in Percona Server a tablespace is "system" (i.e. does not belong to any specific database) if it is either ibdata1 (with space id 0), or a separate doublewrite tablespace (with space id 0xFFFFFFE0). The latter tablespace, if present, will result in --apply-log crash with the above assertion failing when preparing an incremental backup.

Related branches

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-237

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.