innobackupex reports non-critical error by 'ls' on --incremental with --no-timestamp
Bug #939451 reported by
Michael Lamertz
This bug report is a duplicate of:
Bug #1116177: Fix warnings reported by "use warnings FATAL => 'all'".
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Low
|
Alexey Kopytov | ||
| 2.0 |
Triaged
|
Low
|
Unassigned | ||
| 2.1 |
Triaged
|
Low
|
Alexey Kopytov | ||
Bug Description
When using --incremental in combination with --no-timestamp, the 'ls'-Command in line 1774 references $backup_root which does not yet exist at that moment.
Since the result is only needed in the following else clause, the 3 statements around the 'ls' can be placed inside this 'else' which fixes the error message.
The fix is purely cosmetical, since the error of ls has no further consequences besides giving wrong impressions in the log.
Patch attached.
Revision history for this message
| Michael Lamertz (hu6hzq0zv8-7ao7az9-t16qijz8x5) wrote | #1 |
| Changed in percona-xtrabackup: | |
| importance: | Undecided → Low |
Revision history for this message
| Miguel Angel Nieto (miguelangelnieto) wrote | #2 |
| Changed in percona-xtrabackup: | |
| status: | New → Confirmed |
| tags: | added: contribution |
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #3 |
To post a comment you must log in.
Confirmed:
root@debian:~# innobackupex --incremental /tmp/inc --incremental-
ls: cannot access /tmp/inc: No such file or directory
Patch works perfect:
root@debian:~# innobackupex --incremental /tmp/inc --incremental-
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
Tested with the latest 2.0.4