Re: [PATCH manager v2 2/2] fix #7339: lvmthick: ui: add UI fields for option to free storage

["Michael Köppl" <m.koeppl@proxmox.com>]

On Thu Apr 16, 2026 at 4:37 PM CEST, Lukas Sichert wrote:
> In the previous commit the backend recieved the functionality to discard

nit: this would probably be fixed on apply anyway, but this still
mentions a "previous commit" that will not be in pve-manager but
pve-storage, so this part of the commit message won't make any sense
later on.

> allocated space of a VM disk on a SAN, when a VM is deleted. The backend
> checks whether to use this option by parsing storage.cfg to see if
> 'issue_blkdiscard' is set to 1. This variable will automatically be

nit: s/issue_blkdiscard/issue-blkdiscard

> stored into the config file if it is present in the 'PUT' API request.
> To be able to append this to the API call, the variable needs
> to be defined in the json-Schema, but this has also been added in the
> previous commit.

nit: same as above with "previous commit"

>
> To enable a option to free storage in the Gui, create a checkbox with
> the name 'issue_blkdiscard'. In the checkbox use cbind to evaluate

nit: s/issue_blkdiscard/issue-blkdiscard

> 'iscreate' from the component, to only autoenable on new creations of
> LVM Storages. This checkbox also adds the 'issue_blkdiscard'
> variable and its value to the return call.
>
> Also add remappings for the description of the new worker tasks, to show
> in the Gui, which options are used for the current deletion.
>
> Signed-off-by: Lukas Sichert <l.sichert@proxmox.com>
> ---
>  www/manager6/Utils.js           |  3 +++
>  www/manager6/storage/LVMEdit.js | 15 +++++++++++++++
>  2 files changed, 18 insertions(+)
>
> diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
> index b36e46fd..03558942 100644
> --- a/www/manager6/Utils.js
> +++ b/www/manager6/Utils.js
> @@ -2133,6 +2133,9 @@ Ext.define('PVE.Utils', {
>              clusterjoin: ['', gettext('Join Cluster')],
>              dircreate: [gettext('Directory Storage'), gettext('Create')],
>              dirremove: [gettext('Directory'), gettext('Remove')],
> +            diskdiscard: ['', gettext('Discard disk')],
> +            diskzero: ['', gettext('Zero out disk')],
> +            diskzerodiscard: ['', gettext('Zero out and discard disk')],
>              download: [gettext('File'), gettext('Download')],
>              hamigrate: ['HA', gettext('Migrate')],
>              hashutdown: ['HA', gettext('Shutdown')],
> diff --git a/www/manager6/storage/LVMEdit.js b/www/manager6/storage/LVMEdit.js
> index 148f0601..56463bce 100644
> --- a/www/manager6/storage/LVMEdit.js
> +++ b/www/manager6/storage/LVMEdit.js
> @@ -241,5 +241,20 @@ Ext.define('PVE.storage.LVMInputPanel', {
>              uncheckedValue: 0,
>              fieldLabel: gettext('Wipe Removed Volumes'),
>          },
> +        {
> +            xtype: 'proxmoxcheckbox',
> +            name: 'issue-blkdiscard',
> +            uncheckedValue: 0,
> +            cbind: {
> +                checked: '{isCreate}',

I'm not sure about this. Can't a user have an LVM storage on a storage
device that simply doesn't support blkdiscard? AFAICT, in that case a
warning would be printed, but I'm not sure it makes sense to enable this
by default. The bugzilla entry also mentions this as an opt-in flag.

> +            },
> +            fieldLabel: gettext('Discard Removed Volumes'),
> +            autoEl: {
> +                tag: 'div',
> +                'data-qtip': gettext(
> +                    'Enable to issue discard (TRIM) requests for logical volumes before removing them.',
> +                ),
> +            },
> +        },
>      ],
>  });