xtrabackup-2.0: This does not look like a tar archive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Not sure if this belongs here or in XtraDB Cluster:
When trying to get xtrabackup SST (xtrabackup installed from RPM, mysql binaries from Percona XtraDB Cluster 5.5.20 replease), the following happened:
donor:
120407 8:13:28 [Note] WSREP: Running: 'wsrep_
120407 8:13:28 [Note] WSREP: sst_donor_thread signaled with 0
120407 8:13:38 [Note] WSREP: 1 (ip-10-
slave:
120407 8:13:28 [Note] WSREP: Running: 'wsrep_
ute.amazonaws.com' '' '/var/lib/mysql/' '/etc/my.cnf' '2479' 2>sst.err'
120407 8:13:28 [Note] WSREP: Prepared SST request: xtrabackup|
onaws.com:
...
120407 8:13:38 [ERROR] WSREP: Process completed with error: wsrep_sst_
-2-242.
ch file or directory)
slave sst.err:
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Does xtrabackup still require special tar binary? If so, it probably should be a part of the package.
XtraBackup 2.0 does not require a special tar binary, but tar archives produces with --stream=tar still have to be extracted with the -i switch as previously, see http:// www.percona. com/doc/ percona- xtrabackup/ innobackupex/ streaming_ backups_ innobackupex. html
I don't see what happened from the log. The record before the "This does not look like a tar archive" error says something had failed with errno 2. Could it be the culprit?
I'd like to see the xtrabackup command line to investigate this further.