From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id DEF391FF142 for ; Fri, 03 Jul 2026 14:45:08 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id E5C6F21255; Fri, 03 Jul 2026 14:45:07 +0200 (CEST) From: Fiona Ebner To: pve-devel@lists.proxmox.com, =?UTF-8?q?Michael=20K=C3=B6ppl?= Subject: applied: [PATCH container/qemu-server v10 00/10] fix #3711 and adapt drive detach/remove behavior Date: Fri, 3 Jul 2026 14:44:52 +0200 Message-ID: <178308237298.133234.6445363936266889934.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260701141339.181276-1-m.koeppl@proxmox.com> References: <20260701141339.181276-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1783082695833 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.125 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: E6SMQ5FO7OLLF2HWAAOYDXHP6AVYDXVV X-Message-ID-Hash: E6SMQ5FO7OLLF2HWAAOYDXHP6AVYDXVV X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 01 Jul 2026 16:13:29 +0200, Michael Köppl wrote: > This series aims to fix #3711 [0] and streamline the detach/remove > behavior around volumes that are either mounted into a container or > attached to a VM as a hard disk. It also adds warnings in case a > volume's underlying storage does not exist anymore. It is a > continuation of a series from 2022 [1], but makes the following changes: > > [...] Applied, thanks! Changed one log message in each repo slightly to clarify that the volume is removed from the config (and not from somewhere else). pve-container: [01/10] fix #3711: warn about storage errors during mountpoint delete commit: 2b964d0f583dd585b06b09fb3025425093d4112a [02/10] destroy_lxc, delete_mp_volume: rename $volume to $volid commit: a7b7505e9ba290f61f286d5d42937a881d94bf14 [03/10] config: ensure valid volid through parse_volume() commit: 613e12a9ea01dda6c8adb3ebd6e84720c69120f8 [04/10] lxc config: add helper for parsing volid and checking if storage exists commit: 032a73a73572704b58613f86899d9517b505f286 [05/10] allow pending mount point changes if storage is gone commit: 1f6c6dc307e84cd1e211a437e211ffd9ff2b8196 [06/10] destroy template: add early check for linked clones of volumes commit: ca9c3142962cc1e5d0045698d16481485fa1de16 qemu-server: [07/10] adapt linked clone check to not die if an error occurs during check commit: 59e112351cca26f5d0e3f902752ece73193a25a7 [08/10] fix #3711: make removal of VM possible if store does not exist anymore commit: 2e85e6d7f4dd54f4bf8e9a6fbfb25bdb43f7683c [09/10] destroy_vm: use log_warn for vdisk_free errors for consistency commit: 42e450dc03c3d05c4fbd1af9b32c678575c39a93 [10/10] display warnings for storage errors or if storage no longer exists commit: 5b5c576886fbbe79be52c977f9c7ba79a5bfa39f