innobackupex unnecessarily calls 'cp' for metadata files
Bug #1211263 reported by
Ryan Gordon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
George Ormond Lorch III | ||
| 2.1 |
Fix Released
|
High
|
George Ormond Lorch III | ||
| 2.2 |
Fix Released
|
High
|
George Ormond Lorch III | ||
Bug Description
[In:Percona XtraBackup]
It appears that a regression was introduced in xtrabackup 2.1.4 which does not respect the --rsync option any more. If the --rsync option is passed "cp -R" is still used. This is a problem mainly because many NFS do not allow the preservation of certain attributes onto the NFS
innobackupex: Created backup directory /abc/
cp: preserving permissions for `/abc/backup-
innobackupex: Error: Failed to copy file 'backup-my.cnf': 256 at /def/innobackupex line 416.
Thanks,
Ryan
Related branches
lp:~gl-az/percona-xtrabackup/bug1211263
- Alexey Kopytov (community): Approve
-
Diff: 61 lines (+30/-10)2 files modifiedinnobackupex (+17/-9)
test/t/ib_rsync.sh (+13/-1)
Revision history for this message
| Alexey Kopytov (akopytov) wrote | #1 |
| summary: |
- [Regression] rsync option is no longer respected + innobackupex unnecessarily calls 'cp' for metadata files |
| tags: | removed: doc |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
The --rsync option is respected in 2.1.4 (otherwise the error would occur much earlier).
But it's still a regression, because innobackupex in 2.1.4 unnecessarily runs 'cp' to copy backup metadata files. Previously, it would just write those files directly. In 2.1.4 it first copies them to temporary files, and then calls 'cp' to copy them to the final location.