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

Reported by Alexey Kopytov on 2012-10-15
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Critical
Sergei Glushchenko
2.0
Critical
Sergei Glushchenko
2.1
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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers