From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] partially fix #3056: namespace vzdump tmpdir with vmid
Date: Thu, 22 Oct 2020 18:53:42 +0200 [thread overview]
Message-ID: <9bab6eba-c283-1f9e-2eba-4d17eaecfad9@proxmox.com> (raw)
In-Reply-To: <20201019141525.5480-1-d.csapak@proxmox.com>
On 19.10.20 16:15, Dominik Csapak wrote:
> this fixes an issue where a rogue running backup would upload the vm
> config of a later backup in a backup job
>
> instead now that directory gets deleted and the config is not
> available anymore
>
> we cannot really keep those directories around until the end of the
> backup job, since we temporarily save ct contents there, which could get
> large very fast
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> PVE/VZDump.pm | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2020-10-22 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 14:15 [pve-devel] " Dominik Csapak
2020-10-20 7:13 ` Fabian Grünbichler
2020-10-22 16:53 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9bab6eba-c283-1f9e-2eba-4d17eaecfad9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox