xtrabackup creates large tmp file

[monty solomon]

I upgraded from xtrabackup 2.4.5 to 2.4.6 and got paged for the root disks filling up. What changed in version 2.4.6 with respect to the tmpdir? How can I configure it to use a different tmpdir ?

innobacku 8605 root 5u REG 202,1 23074583552 444478 /tmp/xbtempJvdsF8 (deleted)

innobacku 8605 root 5u REG 202,1 23274554880 444478 /tmp/xbtempJvdsF8 (deleted)

innobacku 8605 root 5u REG 202,1 24379669504 444478 /tmp/xbtempJvdsF8 (deleted)

[monty solomon (monty+launchpad)]

CentOS release 6.9 (Final)

[monty solomon (monty+launchpad)]

In version 2.4.5 it used the tmpdir specified in /etc/my.cnf

[monty solomon (monty+launchpad)]

Why does it continue to write to a deleted file?

[Sergei Glushchenko (sergei.glushchenko)]

Is it prepare or backup? What exact command are you using? Note that innobackupex is deprecated. See also bug 1706314

[monty solomon (monty+launchpad)]

innobackupex --slave-info --stream=tar ./

[Sergei Glushchenko (sergei.glushchenko)]

Do you think it is a duplicate of bug 1706314?

[Launchpad Janitor (janitor)]

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1475