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 C6CCB1FF0AF for ; Fri, 06 Nov 2026 01:53:43 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 52850219AB; Fri, 06 Nov 2026 01:51:07 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v3 docs 43/76] storage: lvm: note the rescan after extending a shared volume group Date: Fri, 6 Nov 2026 00:31:18 +0100 Message-ID: <20261105233336.2178064-44-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261105233336.2178064-1-t.lamprecht@proxmox.com> References: <20261105233336.2178064-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: 1793926180380 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.322 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: UJWIIF3O3G5CZLSXDPTHOZV7P2WZWVZ6 X-Message-ID-Hash: UJWIIF3O3G5CZLSXDPTHOZV7P2WZWVZ6 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: LVM hints can hide a PV added by another node to an existing shared volume group. Automatic discovery only retries groups missing entirely, not groups with missing PVs. Document how to rescan after extending a shared group, including that the rescan resets LVM autoactivation records. Signed-off-by: Thomas Lamprecht --- pve-storage-lvm.adoc | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc index ba78663..f00688d 100644 --- a/pve-storage-lvm.adoc +++ b/pve-storage-lvm.adoc @@ -121,6 +121,15 @@ A benefit of LVM is that it can be used with shared storage. For example, an iSCSI LUN. The backend implements proper cluster-wide locking if the storage is marked as shared in the configuration. +NOTE: If you extend a shared volume group onto another device on one node, the +other nodes may only see the added physical volume after LVM has scanned their +devices again, for example with `pvscan --cache`. This command also resets the +autoactivation records of LVM, which can let LVM activate logical volumes on its +own later. {pve} disables autoactivation for the logical volumes it creates. +Before you run the command, make sure that autoactivation is also disabled for +all other logical volumes of the volume group, for example with +`lvchange --setautoactivation n /`. + TIP: You can use the LVM-thin backend for non-shared local storage. It supports snapshots and linked clones. -- 2.47.3