--- Begin Message ---
and mention the different tools used for saferemove to choose the right
option for configuration.
Signed-off-by: Alwin Antreich <[email protected]>
---
I've added th is patch in response to:
https://lore.proxmox.com/all/[email protected]/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
--- End Message ---
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
