Comment 0 for bug 1272329

Revision history for this message
maxadamo (massimilianoadamo) wrote :

I am using percona-xtrabackup-2.1.6-702.rhel6.x86_64 in conjunction with Galera Replication and Percona XtraDB Engine.

MySQL uses innobackupex to perform SST (State Snapshot Tranfer) from one node to the others, and innobackupex is run as user mysql (we don't want to run mysql as root).
If a directory not accessible by the user is found under MySQL "datadir" innobackupex will die.
A common case, is the 'lost+found' directory which is owned by root and has permissions 0700

I don't have the logs with me, but it's just easy to reproduce:
1) mkdir ~mysql/blahblah
2) chown root:root ~mysql/blahblah
3) chmod 700 ~mysql/blahblah
4) run innobackupex as user mysql

Of course, there should not be such a weird directory, but in the case of 'lost+found' there shgould be an exception.

The fix that makes much more sense to me, is to have an exception for such directory (nobody will call a schema with such name).
It would be acceptable to have an option to exclude a specific directory, but this option should be understandable by Galera, and writable to MySQL configuration file.