From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
To: pve-user@lists.proxmox.com
Cc: Eneko Lacunza <elacunza@binovo.es>
Subject: Re: [PVE-User] Feature request : warning / error on migration if target storage doesn't have enough size
Date: Wed, 14 Jan 2026 09:53:02 +0100 [thread overview]
Message-ID: <mailman.351.1768380822.353.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <2055830016.1027915.1768316350277.JavaMail.zimbra@cemea.asso.fr>
[-- Attachment #1: Type: message/rfc822, Size: 7168 bytes --]
From: Eneko Lacunza <elacunza@binovo.es>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Feature request : warning / error on migration if target storage doesn't have enough size
Date: Wed, 14 Jan 2026 09:53:02 +0100
Message-ID: <47f7fa71-68d0-4b57-9187-d8674622aa50@binovo.es>
Hi Guillaume,
Something like you said could be helpful, but some storages have thin
provisioning+deduplication and Proxmox may not be able to determine
effective disk size; so I don't think a hard error would be possible
always (it could prevent migrating VMs that have enough space in
destination although not being evident...
Regards
El 13/1/26 a las 15:59, Guillaume VANDENHOVE escribió:
> Hello,
>
> When migrating a VM (or a container) from one node to another, I miscalculated the remaining empty space on my target node, and ended up with a completely full disk, which is obviously not something you want.
>
> Proxmox already issue warnings like "large storage, migrating may take a while", and it can also issue blocking errors, like "local CD attached to VM". Adding a check of [current VM size] vs [remaining space on target dataset] would be helpful, and a good way to avoid shooting yourself in the foot (which proxmox usually does pretty well). There could be a warning when the target dataset will be almost entirely filled (>97% usage), and an error when the target dataset isn't big enough to migrate the VM.
>
> I'm sorry if this is not the correct place to report this, but I didn't see any "feature request" subforum on the proxmox forum.
>
> Regards,
>
> Guillaume Vandenhove
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project
Tel. +34 943 569 206 | https://www.binovo.es
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2026-01-14 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 14:59 Guillaume VANDENHOVE
2026-01-14 8:53 ` Eneko Lacunza via pve-user [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=mailman.351.1768380822.353.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=elacunza@binovo.es \
/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