xtrabackup fails on apply-log when filesystem doesn't support linux aio

Bug #1065561 reported by Andrew Kuhnhausen on 2012-10-11
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov
Fix Released
Alexey Kopytov

Bug Description

I am currently running the most recent version of zfsonlinux 0.6.0-r11, which does not support AIO. To fix this for mysql to work, I have included the following line in my.cnf:
innodb_use_native_aio = 0

I can backup my databases using innobackupex/xtrabackup, but when using apply-log, xtrabackup doesn't understand that innodb option. Here is the error output:

121011 9:21:03 InnoDB: Using Linux native AIO
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Doing recovery: scanned up to log sequence number 37888453335 (9 %)
121011 9:21:04 InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 378.

I'm running xtrabackup version 2.0.3, percona-server-server-5.5 5.5.27-28.1-log on ubuntu precise, directly pulled from your percona apt repo.

Related branches

Alexey Kopytov (akopytov) wrote :

It's basically MySQL bug http://bugs.mysql.com/bug.php?id=58421. It was fixed upstream in 5.5.21, while XtraBackup is currently based on 5.5.17. This will be fixed when XtraBackup is rebased on recent MySQL / Percona Server versions.

I think the workaround is to use xtrabackup --prepare (i.e. without the innobackupex wrapper) and use --innodb-use-native-aio=0.

tags: added: i26761
Alexey Kopytov (akopytov) wrote :

Unfortunately the suggested workaround doesn't work because of bug #1068459.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-856

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.