Percona XtraBackup moved to https://jira.percona.com/projects/PXB

Rebase XtraBackup on server version where bug #1080741 is fixed

Series 2.1
Bug #1078359

Bug #1078359 reported by Dan Rogers on 2012-11-13

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB	Fix Released	Medium	Alexey Kopytov	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1.4
2.0	Won't Fix	Medium	Unassigned
2.1	Fix Released	Medium	Alexey Kopytov	Percona XtraBackup moved to https://jira.percona.com/projects/PXB 2.1.4

Bug Description

When trying to run a backup using xtrabackup_55 I get a crash almost immediately after starting:

# xtrabackup_55 --backup
xtrabackup_55 version 2.0.3 for Percona Server 5.5.16 Linux (x86_64) (revision id: 470)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /mysqlroot/mysql/datadir
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = /mysqlroot/mysql/innodb
xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
xtrabackup: innodb_log_group_home_dir = /mysqlroot/mysql/innodb
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 4294967296
121113 10:54:10 InnoDB: Using Linux native AIO
xtrabackup: using ALL_O_DIRECT
121113 10:54:11 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
121113 10:54:13 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_native_aio = off in my.cnf
Segmentation fault (core dumped)

Just running 'xtrabackup --backup' correctly starts a backup.

I've attached the my.cnf and core file.

Related branches

lp://staging/~akopytov/percona-xtrabackup/rebase-2.1-on-newer-server-versions

Merged into lp://staging/percona-xtrabackup/2.1 at revision 630

Laurynas Biveinis (community): Approve on 2013-07-23

Revision history for this message

Dan Rogers (drogers-l) wrote on 2012-11-13:

my.cnf from affected server Edit (4.3 KiB, text/plain)

Revision history for this message

Dan Rogers (drogers-l) wrote on 2012-11-13:

Core file. Edit (752.3 KiB, application/octet-stream)

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2012-11-15:

Dan,

It is an InnoDB bug: http://bugs.mysql.com/bug.php?id=61575

The workaround is to set /proc/sys/fs/aio-max-nr to a higher value according to http://dev.mysql.com/doc/innodb/1.1/en/innodb-performance-aio-linux.html

In XtraBackup 2.0.4 (with bug #1068459 fixed) it will also be possible to disable native AIO, as it is not actually used at the --backup stage anyway.

Changed in percona-xtrabackup:
status:	New → Invalid

Revision history for this message

Dan Rogers (drogers-l) wrote on 2012-11-19:

The work-around you suggested does work, but shoudn't xtrabackup handle that more gracefully?

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2012-11-19:

It should, but the problem is in the InnoDB/XtraDB code, so it should be fixed there, and then XtraBackup should be rebased on the server version where it is fixed.

But you are right, this bug should be to track rebasing on a new server version. I've reported the server bug as bug #1080741.

Changed in percona-xtrabackup:
status:	Invalid → Confirmed
summary:	- SEGV in xtrabackup_55 + Rebase XtraBackup on server version where bug #1080741 is fixed

Revision history for this message

Dan Rogers (drogers-l) wrote on 2012-11-19:

Thank you.

Revision history for this message

Alexey Kopytov (akopytov) wrote on 2012-11-27:

In fact http://bugs.mysql.com/bug.php?id=61575 was fixed in MySQL 5.5.21. So the only thing left is rebasing XtraBackup on the current Percona Server 5.5, which is currently based on 5.5.16-22.0.