innobackupex dies if a directory is not readable. i.e.: lost+found
|Percona XtraBackup||Status tracked in 2.4|
I am using percona-
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 under the MySQL "datadir" is not accessible by the user, 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) install -g root -o root -m 0700 -d ~mysql/blahblah
2) run innobackupex as user mysql
Of course, there should not be such a weird directory, but in the case of 'lost+found' there should 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.