innobackupex --copy-back fails with an empty innodb-data-home-dir
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Low
|
Alexey Kopytov | ||
1.6 |
Won't Fix
|
Low
|
Unassigned | ||
2.0 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.1 |
Fix Released
|
High
|
Alexey Kopytov | ||
2.2 |
Fix Released
|
Low
|
Alexey Kopytov |
Bug Description
According to http://
"
If you specify the value as an empty string, you can use absolute file paths in innodb_
"
However, innobackupex --copy-back will fail with the following error if the value of innodb_
"
Original InnoDB data directory does not exist! at /Users/
"
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/
"
Indeed, the root directory is not empty, but it should not be :) We should not complain about it if innodb_
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 183 lines (+111/-9)3 files modifiedinnobackupex.pl (+47/-9)
test/t/bug1049291.sh (+23/-0)
test/t/bug382742.sh (+41/-0)
- Alexey Kopytov (community): Approve
-
Diff: 183 lines (+111/-9)3 files modifiedxtrabackup/innobackupex.pl (+47/-9)
xtrabackup/test/t/bug1049291.sh (+23/-0)
xtrabackup/test/t/bug382742.sh (+41/-0)
Changed in percona-xtrabackup: | |
status: | New → Triaged |
Changed in percona-xtrabackup: | |
importance: | Undecided → Low |
tags: | added: pxc |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/ /jira.percona. com/browse/ PXB-84