tar4ibd crashes on multi-file tablespace files

Reported by Alexey Kopytov on 2011-11-17
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Undecided
Alexey Kopytov
1.6
Undecided
Alexey Kopytov
2.0
Undecided
Alexey Kopytov

Bug Description

tar4ibd may crash on data files in a multi-file system tablespace configuration.

The reason is that tar4ibd expects to read page size from the FSP header of each data file, which, in case of a multi-file system tablespace, is only available in the first file, but not in subsequent ones. For example, for innodb_data_file_path=ibdata1:2000M;ibdata2:10M:autoextend, only ibdata1 will have an FSP header and thus flags, they will be missing in ibdata2. That results in tar4ibd using a bogus page size, hence the crash.

Alexey Kopytov (akopytov) wrote :

There are more details in issue #18185.

On Thu, 17 Nov 2011 06:47:16 -0000, Alexey Kopytov <email address hidden> wrote:
> There is a report that tar4ibd may crash on datafiles produced by 5.0.
> We have to test it by running some streaming backups tests against 5.0,
> both MySQL and Percona Server and fix any issues we may find.

Maybe assign to Patrick to be able to come up with test/infrastructure
to also run against 5.0.

--
Stewart Smith

Assigning to myself while I cook up a testcase. Shouldn't be too terrible to make this happen.

Changed in percona-xtrabackup:
assignee: nobody → Patrick Crews (patrick-crews)
Changed in percona-xtrabackup:
assignee: Patrick Crews (patrick-crews) → Alexey Kopytov (akopytov)
status: New → In Progress
Alexey Kopytov (akopytov) wrote :

Could reproduce the crash on a 5.0 data file provided by a customer.

summary: - Test tar4ibd on 5.0 data files
+ tar4ibd fails on datafiles generated on 5.0

This bug is in fact not specific to 5.0-generated files. Any server using a multi-file system tablespace is affected.

The reason is that tar4ibd expects to read page size from the FSP header of each data file, which, in case of a multi-file system tablespace, is only available in the first file, but not in subsequent ones. For example, for innodb_data_file_path=ibdata1:2000M;ibdata2:10M:autoextend, only ibdata1 will have an FSP header and thus flags, they will be missing in ibdata2. That results in tar4ibd using a bogus page size, hence the crash.

Changing summary and description to reflect the above.

summary: - tar4ibd fails on datafiles generated on 5.0
+ tar4ibd crashes on multi-file tablespace files
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers