I have a gluster 3.2 filesystem I'm using for storage, mounted using the
gluster native mount (as opposed to nfs) for performance, and I'm perfoming
backups of a mysql-5.5.15-linux2.6-x86_64 server on Fedora release 10 with
innobackupex (InnoDB Backup Utility v1.5.1-xtrabackup) as described in the
Percona documentation. I get tons of these messages printed for both full
backup and prepare stages:
111006 17:01:31 InnoDB: Failed to set O_DIRECT on file
./myPorkyDB/myPorkyTable.ibd: OPEN: Invalid argument, continuing anyway
111006 17:01:31 InnoDB: O_DIRECT is known to result in 'Invalid argument' on
Linux on tmpfs, see MySQL Bug#26662
A little later on in each process I get:
111006 17:01:35 innobackupex: completed OK!
Does this mean that the backup succeeded irrespective of the messages
regarding the failure to set O_DIRECT since it was able to complete the
backup by "continuing anyway"?
Thank you for your time,