--extra-lsndir expects an absolute path as a parameter
Bug #1133222 reported by
Nikola Petrov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Low
|
Unassigned | ||
| 2.0 |
Won't Fix
|
Low
|
Unassigned | ||
| 2.1 |
Triaged
|
Low
|
Unassigned | ||
| 2.2 |
Triaged
|
Low
|
Unassigned | ||
| 2.3 |
Triaged
|
Low
|
Unassigned | ||
Bug Description
The --extra-lsndir accepts an absoolute path as a parameter which wasn't obvious from the documentation(at least to me). Please make this more clear or change it to accept a relative path too. Here is an example run:
#pwd
-> /data
#innobackupex --extra-
#ls backups | grep xtrabackup_
-> returns nothing
#innobackupex --extra-
#ls backups | grep xtrabackup_
-> a match
| tags: |
added: doc removed: documentation |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #2 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
I think innobackupex should disallow relative paths for --extra-lsndir (as it unclear which directory it should be relative to, and no matter how it is defined, it will be confusing). And then this fact should be reflected in docs as well.