From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Sichert <l.sichert@proxmox.com>
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 [thread overview]
Message-ID: <179479297123.3274416.8199304055007015923.b4-ty@b4> (raw)
In-Reply-To: <20260811150534.137170-1-l.sichert@proxmox.com>
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
prev parent reply other threads:[~2026-11-16 1:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 15:05 [PATCH docs/manager/storage v12 0/6] fix #7339: lvmthick: add option to free storage for deleted VMs Lukas Sichert
2026-08-11 15:05 ` [PATCH storage v12 1/6] lvm: saferemove: keep LVs where zero-out failed for manual zero-out Lukas Sichert
2026-08-11 15:05 ` [PATCH storage v12 2/6] lvm: saferemove: zero out volumes range by range Lukas Sichert
2026-08-11 15:05 ` [PATCH storage v12 3/6] lvm: saferemove: make throughput an integer property Lukas Sichert
2026-08-11 15:05 ` [PATCH storage v12 4/6] fix #7339: lvm: add discard action for removed volumes Lukas Sichert
2026-08-11 15:05 ` [PATCH manager v12 5/6] fix #7339: lvm: add discard-on-remove option to UI Lukas Sichert
2026-08-11 15:05 ` [PATCH docs v12 6/6] fix #7339: lvm: document discard option Lukas Sichert
2026-09-09 8:27 ` [PATCH docs/manager/storage v12 0/6] fix #7339: lvmthick: add option to free storage for deleted VMs Thomas Ellmenreich
2026-10-06 8:33 ` Michael Köppl
2026-11-16 1:36 ` Thomas Lamprecht [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=179479297123.3274416.8199304055007015923.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=l.sichert@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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