--- Begin Message ---
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
[email protected]
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/
--- End Message ---
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
