From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Matthias Heiserer <m.heiserer@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu-server v4] fix 3886: QEMU restore: verify storage allows images before writing
Date: Thu, 24 Feb 2022 13:33:21 +0100 [thread overview]
Message-ID: <56e39079-4d65-575b-631a-2f2f508cca35@proxmox.com> (raw)
In-Reply-To: <20220224104559.382734-1-m.heiserer@proxmox.com>
On 24.02.22 11:45, Matthias Heiserer wrote:
> When restoring a backup and the storage the disks would be created on
> doesn't allow 'images', the process errors without cleanup.
> This is the same behaviour we currently have when the storage is
> disabled.
>
> Adds the Datastore.AllocateSpace check to cloudinit drives.
that belongs in a separate patch, I split that out.
>
> Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
Please pick up T-b/R-b tags from earlier reviews if the patch did not change
substantially in between - thx!
> ---
> Thanks to Fabian!
> Changes from v3:
> + Restore a line I accidentally deleted
>
> Changes from v2:
> + Also check Datastore.AllocateSpace permissions for cloudinit device
> + Move content type check closer to allocate permission check
>
> Changes from v1:
> + Check content type for cloud init drives
>
> PVE/QemuServer.pm | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
>
applied, thanks! Followed up with using a closure for the shared checks, not
less lines of code but slightly less noise in the looping over backup config
part.
prev parent reply other threads:[~2022-02-24 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:45 [pve-devel] " Matthias Heiserer
2022-02-24 12:33 ` 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=56e39079-4d65-575b-631a-2f2f508cca35@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.heiserer@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