From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id E23FE1FF0E1 for ; Mon, 16 Nov 2026 02:36:30 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 04DCB21748; Mon, 16 Nov 2026 02:36:29 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Lukas Sichert Subject: applied: [PATCH docs/manager/storage v12 0/6] fix #7339: lvmthick: add option to free storage for deleted VMs Date: Mon, 16 Nov 2026 02:36:13 +0100 Message-ID: <179479297123.3274416.8199304055007015923.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260811150534.137170-1-l.sichert@proxmox.com> References: <20260811150534.137170-1-l.sichert@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: 1794792983836 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.078 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 RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: GBQYSYLNRSYZAJGDGJH26TPBPZYKQVMC X-Message-ID-Hash: GBQYSYLNRSYZAJGDGJH26TPBPZYKQVMC X-MailFrom: t.lamprecht@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 Tue, 11 Aug 2026 17:05:01 +0200, Lukas Sichert wrote: > Logical volumes (LV) in an LVM (thick) volume group (VG) are > thick-provisioned, but the underlying backing storage can be > thin-provisioned. In particular, this can be the case if the VG resides > on a LUN provided by a SAN via iSCSI/FC/SAS [1], where the LUN may be > thin-provisioned on the SAN side. > > In such setups, one usually wants that deleting an LV (e.g. VM disk) > frees up space on the SAN side, especially when using > snapshots-as-volume-chains, because snapshot LVs are thick-provisioned > LVs from the LVM point of view, so users may want to over-provision the > LUN on the SAN side. > > [...] Applied, thanks! [docs] applied to git/pve-docs.git (master) [1/1] fix #7339: lvm: document discard option https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=416c52d6d8c2f31f25842de5c2bbe294ff8b9f15 [manager] applied to pve-manager.git (master) [1/1] fix #7339: lvm: add discard-on-remove option to UI https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=a03c23750d5e0e47c263614b7ac1664ce594a3b6 [storage] applied to pve-storage.git (master) [1/4] lvm: saferemove: keep LVs where zero-out failed for manual zero-out https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=795c173aaefa4b583b88088506452fa68ba30c20 [2/4] lvm: saferemove: zero out volumes range by range https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=52a6914d9d174b0c43f6eaaf99b64eedefdb1174 [3/4] lvm: saferemove: make throughput an integer property https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=a618f24d6e4017b66bd2b77fac699af0b81de507 [4/4] fix #7339: lvm: add discard action for removed volumes https://git.proxmox.com/?p=pve-storage.git;a=commitdiff;h=b86d7c9256f67e60100cc026856a0c99e383e7af