From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 310441FF13B for ; Tue, 13 Jan 2026 15:59:17 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7EE8A1B06F; Tue, 13 Jan 2026 15:59:14 +0100 (CET) DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=cemea.asso.fr; q=dns/txt; s=email; t=1768316351; x=1768323551; h=Content-Transfer-Encoding: Content-Type: MIME-Version: Subject: Subject: Message-ID: To: To: From: From: Date: Sender: Sender; bh=RYlL680tTtre+d78idGIzBzobRmmYqL2ZlNLDTceKSo=; b=KQzwuXplObXjNpA4sGQ6/VBIWrcuvoJbo+NjopV+E0Si7cenB1TdlTGTtTkJ9raELPAPDFrEQYV5EDVGwm1LNhSM9/VXFfleOKUJZA8P/SyIO13pEsHTbKGomcmI2bq9QUzWDRdHpWQrIomZSp4fAhyLb8OTZLTbcp1SUfm8RPQ= X-Mailgun-Sid: WyI2N2ZmOCIsInB2ZS11c2VyQGxpc3RzLnByb3htb3guY29tIiwiYzNkZmYzIl0= X-Mailgun-Sending-Ip: 198.244.61.214 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cemea.asso.fr; h=cc:content-transfer-encoding:content-type:content-type:date :from:from:message-id:mime-version:reply-to:subject:subject:to :to; s=mg2mail; bh=RYlL680tTtre+d78idGIzBzobRmmYqL2ZlNLDTceKSo=; b= gbekeJi8D+XFW8QBRxR5+kL8/r/Y/ulKjso3UJpl47KtWbEGwHQfxwBI3x4kZeMY goGO+fFjVDJFkcD5e3xn0eROyFZ+6IRfbEbzSXKD3GV4Cr8Yi4WpLHhZyQtwoo1J SETztV85VdrEEJc90+fmsrwXsb13F0A6pAxq5OWgRigezRYVTmaPIX4NMUfrcVEk yPszAX8TQ5Qv44ycANlC/NPRU83fbebj+GCpovts9CCwDpl2V79Y6HMqd+g11K8X 6UEEyZPRpIabP6gRQOYQyXHRQPQ6/YXATs+Z1sjni8wCd5YJD51+5meO6nsyqcdO Prap2pnlvipQEvHU5cNWDg== X-Virus-Scanned: amavisd-new at mail.cemea.org Date: Tue, 13 Jan 2026 14:59:10 +0000 (UTC) From: Guillaume VANDENHOVE To: pve-user@lists.proxmox.com Message-ID: <2055830016.1027915.1768316350277.JavaMail.zimbra@cemea.asso.fr> MIME-Version: 1.0 X-Originating-IP: [90.63.232.95] X-Mailer: Zimbra 8.8.15_GA_4156 (ZimbraWebClient - FF145 (Linux)/8.8.15_GA_4156) Thread-Index: yjSwOnY8v8XJdsixPmU3ArM81tk5pA== Thread-Topic: Feature request : warning / error on migration if target storage doesn't have enough size X-SPAM-LEVEL: Spam detection results: 0 AWL 0.001 Adjusted score from AWL reputation of From: address BAYES_20 -0.001 Bayes spam probability is 5 to 20% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [cemea.asso.fr] Subject: [PVE-User] Feature request : warning / error on migration if target storage doesn't have enough size X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" 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