[pve-devel] [PATCH docs 2/2] pve-storage-lvm: add saferemove-stepsize

[pve-devel] [PATCH docs 2/2] pve-storage-lvm: add saferemove-stepsize

[Alwin Antreich via pve-devel]

[-- Attachment #1: Type: message/rfc822, Size: 4156 bytes --]

From: Alwin Antreich <alwin@antreich.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs 2/2] pve-storage-lvm: add saferemove-stepsize
Date: Wed, 29 Oct 2025 14:27:45 +0100
Message-ID: <20251029132745.3127244-2-alwin@antreich.com>

and mention the different tools used for saferemove to choose the right
option for configuration.

Signed-off-by: Alwin Antreich <alwin@antreich.com>
---

I've added th is patch in response to:
https://lore.proxmox.com/all/mailman.253.1761222252.362.pve-devel@lists.proxmox.com/T/#u

 pve-storage-lvm.adoc | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
index 527c732..5dd034e 100644
--- a/pve-storage-lvm.adoc
+++ b/pve-storage-lvm.adoc
@@ -43,6 +43,15 @@ When removing a volume, this makes sure that all data gets erased and cannot be
 accessed by other LVs created later (which happen to be assigned the same
 physical extents). This is a costly operation, but may be required as a security
 measure in certain environments.
++
+Storage devices that support the write zeroes operation will use blockdiscard
+to zero blocks. Otherwise, a fallback to cstream is performed.
+
+`saferemove-stepsize`::
+
+Wipe step size in MiB (`blockdiscard -p` paramater value), capped to the maximum
+step size supported by the underlying storage. Up to 32 MiB (maximum) by
+default.
 
 `saferemove_throughput`::
 
-- 
2.39.5




[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel