public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Michal Fox <me@dualfroz.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager] fix #6009: ui: drop the 128 TiB limit for disk sizes
Date: Sun,  4 Oct 2026 14:00:57 +0000	[thread overview]
Message-ID: <20261004140057.7-1-me@dualfroz.com> (raw)

The size fields for creating and resizing disks of VMs and mount points
of containers only accepted up to 128 TiB. The API does not have such a
limit, so larger disks could only be created or resized on the CLI.

Remove the limit from the size fields, like it was done for the memory
fields in commit fdce7d56 ("Remove swap/memory limit in the Manager,
fixes #1799").

Signed-off-by: Michal Fox <me@dualfroz.com>
---
The DB and WAL size fields when creating a Ceph OSD use the same 128 TiB
maximum, but as those are not disk images, I left them as they are.

 www/manager6/form/DiskStorageSelector.js | 1 -
 www/manager6/lxc/MPResize.js             | 1 -
 www/manager6/qemu/HDResize.js            | 1 -
 3 files changed, 3 deletions(-)

diff --git a/www/manager6/form/DiskStorageSelector.js b/www/manager6/form/DiskStorageSelector.js
index 696f9033..b81ac87a 100644
--- a/www/manager6/form/DiskStorageSelector.js
+++ b/www/manager6/form/DiskStorageSelector.js
@@ -164,7 +164,6 @@ Ext.define('PVE.form.DiskStorageSelector', {
                 hidden: me.hideSize,
                 disabled: me.hideSize,
                 minValue: 0.001,
-                maxValue: 128 * 1024,
                 decimalPrecision: 3,
                 value: me.defaultSize,
                 allowBlank: false,
diff --git a/www/manager6/lxc/MPResize.js b/www/manager6/lxc/MPResize.js
index 658123a1..3b737c1c 100644
--- a/www/manager6/lxc/MPResize.js
+++ b/www/manager6/lxc/MPResize.js
@@ -49,7 +49,6 @@ Ext.define('PVE.window.MPResize', {
         me.hdsizesel = Ext.createWidget('numberfield', {
             name: 'size',
             minValue: 0,
-            maxValue: 128 * 1024,
             decimalPrecision: 3,
             value: '0',
             fieldLabel: `${gettext('Size Increment')} (${gettext('GiB')})`,
diff --git a/www/manager6/qemu/HDResize.js b/www/manager6/qemu/HDResize.js
index 574bfb5a..4d9532e5 100644
--- a/www/manager6/qemu/HDResize.js
+++ b/www/manager6/qemu/HDResize.js
@@ -50,7 +50,6 @@ Ext.define('PVE.window.HDResize', {
         me.hdsizesel = Ext.createWidget('numberfield', {
             name: 'size',
             minValue: 0,
-            maxValue: 128 * 1024,
             decimalPrecision: 3,
             value: '0',
             fieldLabel: `${gettext('Size Increment')} (${gettext('GiB')})`,
-- 
2.43.0




                 reply	other threads:[~2026-10-04 14:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261004140057.7-1-me@dualfroz.com \
    --to=me@dualfroz.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal