Created by Alexey Kopytov on 2013-03-05 and last modified on 2013-03-05
Get this branch:
bzr branch lp:~akopytov/percona-xtrabackup/bug870119-2.0
Only Alexey Kopytov can upload to this branch. If you are Alexey Kopytov please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Recent revisions

505. By Alexey Kopytov on 2013-03-05

Bug #870119: assertion failure while trying to read InnoDB partition

The problem was that the InnoDB file I/O subsystem may reuse file
descriptors by closing the old ones when the number of open files hits
innodb_open_files. Which works for InnoDB, because if InnoDB needs to
access a table which has been closed, it would just reopen it.However,
that didn't work for XtraBackup, since it only keeps a file descriptor
when copying a file. So when the --parallel option was used, there was a
chance that another thread wanted to open a file and hit
innodb_open_files. Therefore fil_try_to_close_file_in_LRU() might close
the file descriptor which was currently in use by another thread and
then this descriptor is shortly reused when opening another file. Which
would result in obscure failures like this.

However, most part of the problem disappeared with the fix for bug
: XtraBackup no longer relies on the file descriptors created by
the 'fil' subsystem of InnoDB to get tablespace flags, and that was the
reason for exhausting the innodb_open_files pool. So bug #870119 is
essentially a duplicate, or at least became extremely hard to hit in the

The only thing that should be done to exclude even a theoretical chance
of reusing file descriptors from the 'fil' subsystem is to always create
a new file descriptor to copy the file, instead of checking if a node
has been previously open by the 'fil' subsystem and reusing the
descriptor if so. Which is what this fix implements.

504. By Alexey Kopytov on 2013-03-04

Merge 2.0.5 release branch.

503. By Laurynas Biveinis on 2013-03-03

Fix bug 1142229 (latest merge breaks compiling against mysql-5.1).

The problem is that -fpermissive needs to be defined for 5.0 and
5.1-builtin build configurations. This was done for the build types
"innodb51_builtin" and "innodb50", but not for their synonyms "5.0"
and "5.1".

Fixed by resolving the fully-synonymous build types to their canonical

502. By Alexey Kopytov on 2013-03-02

Merge trunk.

501. By Alexey Kopytov on 2013-02-04

Bug #1114955: xtrabackup_pid remains existed after execution

Fix a regression introduced by the fix for bug #1055989: in case the
xtrabackup process has finished copying the log file and terminated
before wait_for_ibbackup_finish() is called, remove the stale
xtrabackup_pid file.

500. By <email address hidden> on 2013-01-22

Merge lp:~hrvojem/percona-xtrabackup/bug1100008-2.0

499. By Stewart Smith on 2013-01-17

merge 1.6.6 release branch

498. By <email address hidden> on 2013-01-17

Merge lp:~hrvojem/percona-xtrabackup/rn-2.0.5

497. By <email address hidden> on 2013-01-15

Merge lp:~gl-az/percona-xtrabackup/2.0-bug740489

496. By <email address hidden> on 2013-01-14

Merge lp:~sergei.glushchenko/percona-xtrabackup/xb20-bug1095551

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.