xtrabackup as SST fails when innodb_flush_method is O_DIRECT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
Medium
|
Alexey Kopytov | ||
2.1 |
Fix Released
|
Medium
|
Alexey Kopytov | ||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This should be related to https:/
When innodb_flush_method is set to O_DIRECT, it's not possible to use xtrabackup as SST, the error is the following :
120629 6:12:16 InnoDB: Starting shutdown...
120629 6:12:19 InnoDB: Shutdown completed; log sequence number 3351590558
InnoDB: Error: tried to read 2048 bytes at offset 0 0.
InnoDB: Was only able to read 0.
120629 6:12:19 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 operation call: 'read'.
InnoDB: Cannot continue operation.
innobackupex: Error:
innobackupex: ibbackup failed at /usr//bin/
For Percona internal reference check #23358
Workaround:
---------------
copy the my.cnf and in the copy remove innodb_flush_method and force in /usr/bin/
line 65:
-CONF=$5
+CONF=/
Related branches
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 39 lines (+7/-6)1 file modifiedsrc/xtrabackup.cc (+7/-6)
- Sergei Glushchenko (community): Approve (g2)
-
Diff: 39 lines (+7/-6)1 file modifiedsrc/xtrabackup.cc (+7/-6)
Changed in percona-xtradb-cluster: | |
status: | Expired → Incomplete |
Tested with http:// sprunge. us/FAWW config and it works with O_DIRECT flush method.
Complete log: http:// sprunge. us/eMZO