From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Lukas Sichert" <l.sichert@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH manager v6 2/2] fix #7339: lvmthick: ui: add UI option to free storage
Date: Mon, 08 Jun 2026 16:06:03 +0200 [thread overview]
Message-ID: <DJ3Q4S59CAJT.DTPG7NUQ8DZ5@proxmox.com> (raw)
In-Reply-To: <20260522130419.94386-3-l.sichert@proxmox.com>
On Fri May 22, 2026 at 3:04 PM CEST, Lukas Sichert wrote:
[snip]
> column1: [
> {
> xtype: 'pveBaseStorageSelector',
> @@ -241,5 +274,20 @@ Ext.define('PVE.storage.LVMInputPanel', {
> uncheckedValue: 0,
> fieldLabel: gettext('Wipe Removed Volumes'),
> },
> + {
> + xtype: 'proxmoxcheckbox',
> + name: 'on-remove-discard',
> + uncheckedValue: 0,
> + cbind: {
> + checked: '{isCreate}',
I mentioned this on v1 as well, but I'm not sure if enabling this by
default for new LVM storages is a good idea. @Fabian also commented in
v1 "If you don't know what discard means, you should not enable this
option anyway." and the bugzilla issue mentions it as opt-in.
> + },
> + fieldLabel: gettext('Discard Removed Volumes'),
> + autoEl: {
> + tag: 'div',
> + 'data-qtip': gettext(
> + 'Enable to issue discard (TRIM) requests for logical volumes before removing them.',
> + ),
> + },
> + },
> ],
> });
next prev parent reply other threads:[~2026-06-08 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 13:04 [PATCH manager/storage v6 0/2] fix #7339: lvmthick: add option to free storage for deleted VMs Lukas Sichert
2026-05-22 13:04 ` [PATCH storage v6 1/2] fix #7339: lvmthick: add worker to free space of to be " Lukas Sichert
2026-06-08 14:06 ` Michael Köppl
2026-05-22 13:04 ` [PATCH manager v6 2/2] fix #7339: lvmthick: ui: add UI option to free storage Lukas Sichert
2026-06-08 14:06 ` Michael Köppl [this message]
2026-06-08 14:43 ` [PATCH manager/storage v6 0/2] fix #7339: lvmthick: add option to free storage for deleted VMs Michael Köppl
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=DJ3Q4S59CAJT.DTPG7NUQ8DZ5@proxmox.com \
--to=m.koeppl@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