innobackupex --copy-back fails with an empty innodb-data-home-dir

[Alexey Kopytov]

According to http://dev.mysql.com/doc/refman/5.5/en/innodb-parameters.html#sysvar_innodb_data_home_dir an empty string is a valid value for innodb_data_home_dir:

"
If you specify the value as an empty string, you can use absolute file paths in innodb_data_file_path.
"

However, innobackupex --copy-back will fail with the following error if the value of innodb_data_home_dir read from my.cnf is an empty string:

"
Original InnoDB data directory does not exist! at /Users/kaa/src/launchpad/percona-xtrabackup/2.0/innobackupex line 567.
"

Indeed, the directory with an empty name does not exist, but it should skip the check in this case.

If one changes the value in my.cnf to "/" (which is equivalent to an empty string, the error becomes:

"
Original InnoDB data directory is not empty! at /Users/kaa/src/launchpad/percona-xtrabackup/2.0/innobackupex line 571.
"

Indeed, the root directory is not empty, but it should not be :) We should not complain about it if innodb_data_home_dir is an absolute path.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-84