From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id CB84B1FF0DA for ; Thu, 19 Nov 2026 20:50:38 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 5B04321B48; Thu, 19 Nov 2026 20:48:29 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v8 docs 28/43] storage: multipath: describe the use shown for an open LUN Date: Thu, 19 Nov 2026 20:46:33 +0100 Message-ID: <20261119194655.3163258-29-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261119194655.3163258-1-t.lamprecht@proxmox.com> References: <20261119194655.3163258-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: 1795117622996 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.153 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: QTBTLCJ7VZCP2ZN67TAZQMRH4C7W27QL X-Message-ID-Hash: QTBTLCJ7VZCP2ZN67TAZQMRH4C7W27QL 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: The LUN list of a node names the virtual machine or process that has a LUN open for writing, and has a column for the iSCSI target. Both help to find out what a LUN of a third-party storage plugin belongs to. Signed-off-by: Thomas Lamprecht --- pve-storage-multipath.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/pve-storage-multipath.adoc b/pve-storage-multipath.adoc index e56bd92..cadbc76 100644 --- a/pve-storage-multipath.adoc +++ b/pve-storage-multipath.adoc @@ -230,6 +230,14 @@ of a storage and leaves them all out. A LUN that is only listed for its volume group then shows *Unknown* for that node, or is not listed if no node reports it. +*Used By* under *Node -> SAN* names the storage that uses a LUN. Without one, +it names the virtual machine or other process that has the LUN open for +writing, for example a guest that has it as disk from a third-party storage +plugin. Such a LUN can neither be wiped nor selected in a guided setup. A +process that only reads the LUN is not shown, but can still prevent a wipe. +A column that is hidden by default shows the iSCSI target that a LUN is +attached through, or the subsystem of an NVMe namespace. + The *State* of a LUN is the worst known state among its nodes. For a state other than *Optimal*, it names the nodes in that state, unless all nodes are in it. Nodes in *Unknown* do not count for it and are listed after it. Hover over it