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

Bug #1066843 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.

Related branches

lp:~sergei.glushchenko/percona-xtrabackup/BT-26901-2.0
Merged into lp:percona-xtrabackup/2.0 at revision 480
Alexey Kopytov: Approve on 2012-11-15
Laurynas Biveinis: Pending requested 2012-11-15
lp:~sergei.glushchenko/percona-xtrabackup/BT-26901-2.1
Merged into lp:percona-xtrabackup/2.1 at revision 454
Alexey Kopytov: Approve on 2012-11-15
Laurynas Biveinis: Pending requested 2012-11-15
Laurynas Biveinis: Needs Fixing on 2012-10-18
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers