From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH v5 manager 32/36] ui: node: san: wipe a LUN that no storage uses
Date: Mon, 16 Nov 2026 02:23:41 +0100 [thread overview]
Message-ID: <20261116012355.3187417-33-t.lamprecht@proxmox.com> (raw)
In-Reply-To: <20261116012355.3187417-1-t.lamprecht@proxmox.com>
A recycled LUN often still carries a volume group or partitions from
its previous use and cannot be set up again until those are gone. Let
root@pam, the only user the wipe API accepts, wipe a LUN from
Node > SAN.
The dialog shows what the node knows about the content of the LUN and
asks for its name as confirmation. The button is disabled for a LUN
that the list attributes to a storage. The list shows cached state, so
the check that the node does for the wipe itself stays the one that
counts.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
www/manager6/Makefile | 1 +
www/manager6/node/SANLuns.js | 14 ++++++++
www/manager6/window/SANLunWipe.js | 53 +++++++++++++++++++++++++++++++
3 files changed, 68 insertions(+)
create mode 100644 www/manager6/window/SANLunWipe.js
diff --git a/www/manager6/Makefile b/www/manager6/Makefile
index 723007220..19433ef9c 100644
--- a/www/manager6/Makefile
+++ b/www/manager6/Makefile
@@ -137,6 +137,7 @@ JSSRC= \
window/Restore.js \
window/SafeDestroyGuest.js \
window/SafeDestroyStorage.js \
+ window/SANLunWipe.js \
window/Settings.js \
window/Snapshot.js \
window/StartupEdit.js \
diff --git a/www/manager6/node/SANLuns.js b/www/manager6/node/SANLuns.js
index dc659dd24..b290488a6 100644
--- a/www/manager6/node/SANLuns.js
+++ b/www/manager6/node/SANLuns.js
@@ -157,6 +157,20 @@ Ext.define('PVE.node.SANLunList', {
success: reload,
}),
},
+ {
+ xtype: 'proxmoxButton',
+ text: gettext('Wipe'),
+ iconCls: 'fa fa-eraser',
+ disabled: true,
+ enableFn: (rec) => Proxmox.UserName === 'root@pam' && !rec.get('used-by-storage'),
+ handler: (button, event, rec) =>
+ Ext.create('PVE.window.SANLunWipe', {
+ node: me.nodename,
+ lun: rec.data,
+ autoShow: true,
+ taskDone: () => !me.destroyed && reload(),
+ }),
+ },
];
me.callParent();
Proxmox.Utils.monStoreErrors(me, me.rstore);
diff --git a/www/manager6/window/SANLunWipe.js b/www/manager6/window/SANLunWipe.js
new file mode 100644
index 000000000..4d2713996
--- /dev/null
+++ b/www/manager6/window/SANLunWipe.js
@@ -0,0 +1,53 @@
+Ext.define('PVE.window.SANLunWipe', {
+ extend: 'Proxmox.window.Edit',
+ title: gettext('Wipe LUN'),
+ onlineHelp: 'storage_multipath',
+ width: 550,
+ isCreate: true,
+ showProgress: true,
+ submitText: gettext('Wipe'),
+ method: 'PUT',
+
+ initComponent: function () {
+ let me = this;
+ let lun = me.lun;
+ let name = lun.name || lun.wwid;
+ me.url = `/nodes/${me.node}/disks/wipedisk`;
+ me.extraRequestParams = { disk: lun['by-id'] || lun.devpath };
+ me.items = [
+ {
+ xtype: 'component',
+ cls: 'pmx-hint',
+ html: Ext.htmlEncode(
+ Ext.String.format(
+ gettext('Wipe LUN {0} on node "{1}"? All data on the device will be lost!'),
+ name,
+ me.node,
+ ),
+ ),
+ },
+ {
+ xtype: 'displayfield',
+ fieldLabel: gettext('Used By'),
+ value: PVE.SANUtils.usageText(lun),
+ },
+ {
+ xtype: 'displayfield',
+ fieldLabel: gettext('Size'),
+ value: Proxmox.Utils.format_size(lun.size),
+ },
+ {
+ xtype: 'textfield',
+ fieldLabel: Ext.String.format(
+ gettext('Please enter the ID to confirm ({0})'),
+ Ext.htmlEncode(name),
+ ),
+ labelAlign: 'top',
+ submitValue: false,
+ allowBlank: false,
+ validator: (value) => value === name || gettext('The ID does not match.'),
+ },
+ ];
+ me.callParent();
+ },
+});
next prev parent reply other threads:[~2026-11-16 1:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 1:23 [PATCH v5 cluster,storage,docs,manager 00/36] SAN: cluster-wide multipath, SAN views and a guided setup for shared LVM Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 cluster 01/36] cfs: observe the multipath configuration files Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 02/36] diskmanage: collect disk transport type from lsblk Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 03/36] diskmanage: qualify NVMe over fabrics transport Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 04/36] diskmanage: optionally include iSCSI session devices in disk enumeration Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 05/36] diskmanage: collect native NVMe multipath path state Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 06/36] iscsi: factor out session device map from device list Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 07/36] multipath: add a library around multipathd Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 08/36] diskmanage: add helper to list multipath devices Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 09/36] multipath: add a cluster-wide configuration Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 10/36] iscsi: add an option to manage storage LUNs with multipath Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 11/36] lvm: activate a missing base volume before using the volume group Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 12/36] multipath: apply the configuration on every node Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 13/36] multipath: publish per-node status Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 14/36] api: add endpoints for the cluster-wide multipath configuration Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 15/36] api: multipath: add the cluster-wide health status Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 16/36] api: scan: add a SAN LUN inventory Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 17/36] pvesm: expose the " Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 18/36] api: add node-level iSCSI status Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 19/36] disks: lvm: drop unused imports Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 20/36] disks: lvm: allow volume groups on SAN LUNs and multipath maps Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 21/36] disks: lvm: refuse to destroy the volume group of a shared storage Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 storage 22/36] disks: allow wiping a SAN LUN that no storage uses Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 docs 23/36] storage: document the cluster-wide multipath management Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 24/36] pvestatd: apply the multipath configuration and report the node status Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 25/36] report: add the managed multipath configuration Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 26/36] api: cluster: add the multipath endpoints Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 27/36] api: nodes: expose the iSCSI status Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 28/36] ui: dc: add a SAN view Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 29/36] ui: storage: iscsi: add the multipath option Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 30/36] ui: lvm: enable shared when a base storage is selected Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 31/36] ui: node: add SAN LUNs panel Thomas Lamprecht
2026-11-16 1:23 ` Thomas Lamprecht [this message]
2026-11-16 1:23 ` [PATCH v5 manager 33/36] ui: node: san: show iSCSI targets and sessions Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 34/36] ui: dc: san: add a guided setup for shared LVM on iSCSI Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 35/36] ui: dc: san: add a guided setup for shared LVM on Fibre Channel Thomas Lamprecht
2026-11-16 1:23 ` [PATCH v5 manager 36/36] ui: storage: point the iSCSI and LVM add dialogs to the SAN view Thomas Lamprecht
2026-11-18 8:11 ` superseded: [PATCH v5 cluster,storage,docs,manager 00/36] SAN: cluster-wide multipath, SAN views and a guided setup for shared LVM Thomas Lamprecht
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=20261116012355.3187417-33-t.lamprecht@proxmox.com \
--to=t.lamprecht@proxmox.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