xtrabackup fails on apply-log when filesystem doesn't support linux aio
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
Low
|
Alexey Kopytov | ||
2.1 |
Fix Released
|
Low
|
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_
I can backup my databases using innobackupex/
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://
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/
I'm running xtrabackup version 2.0.3, percona-
Related branches
- Stewart Smith (community): Approve
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 51 lines (+19/-0)1 file modifiedsrc/xtrabackup.c (+19/-0)
- Laurynas Biveinis (community): Approve
-
Diff: 4471 lines (+762/-724)12 files modifiedMakefile (+9/-39)
patches/innodb51.patch (+87/-88)
patches/innodb55.patch (+99/-92)
patches/innodb56.patch (+70/-67)
patches/xtradb51.patch (+114/-119)
patches/xtradb55.patch (+238/-228)
src/Makefile (+1/-1)
src/compact.cc (+1/-1)
src/innodb_int.cc (+58/-2)
src/innodb_int.h (+52/-2)
src/xtrabackup.cc (+8/-12)
utils/build.sh (+25/-73)
tags: | added: i26761 |
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.