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 DD9691FF0C0 for ; Wed, 18 Nov 2026 07:56:45 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 67B1F21967; Wed, 18 Nov 2026 07:54:11 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v6 manager 34/42] ui: lvm: enable shared when a base storage is selected Date: Wed, 18 Nov 2026 07:52:51 +0100 Message-ID: <20261118065302.3033937-35-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261118065302.3033937-1-t.lamprecht@proxmox.com> References: <20261118065302.3033937-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794984789084 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.180 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) 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: 7X56JYJEM2E2IQWYNDNZ43ON2P25HSGV X-Message-ID-Hash: 7X56JYJEM2E2IQWYNDNZ43ON2P25HSGV 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: A volume group on a LUN of a base storage is reachable from every node that uses the base storage. Without the shared flag, each node treats it as a local volume group of its own. Allocations are then only serialized per node, and a migration copies the disks as if they were local. The checkbox is off by default and easy to miss. Selecting a base storage checks it, and the admin can still uncheck it. Signed-off-by: Thomas Lamprecht --- www/manager6/storage/LVMEdit.js | 3 +++ 1 file changed, 3 insertions(+) diff --git a/www/manager6/storage/LVMEdit.js b/www/manager6/storage/LVMEdit.js index 9308ef4eb..688130b19 100644 --- a/www/manager6/storage/LVMEdit.js +++ b/www/manager6/storage/LVMEdit.js @@ -211,6 +211,9 @@ Ext.define('PVE.storage.LVMInputPanel', { vgNameField.setVisible(!!value); vgNameField.setDisabled(!value); + + // a volume group on a LUN of a base storage is meant to be shared + me.up('inputpanel').down('field[name=shared]').setValue(!!value); }, }, },