Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-12-07 08:23:42 +03:00
Code Releases Activity

pve-storage-lvm: add saferemove-stepsize

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

Signed-off-by: Alwin Antreich <alwin@antreich.com>
Link: https://lore.proxmox.com/mailman.373.1761744508.362.pve-devel@lists.proxmox.com
[FE: fix typo in command name: blockdiscard -> blkdiscard
     add quotes around commands and operation name]
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
Alwin Antreich via pve-devel
2025-10-29 14:27:45 +01:00
committed by Fiona Ebner
parent 86c30b1b81
commit 17a22102e3
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
pve-storage-lvm.adoc
View File

@@ -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 `blkdiscard`
to zero blocks. Otherwise, a fallback to `cstream` is performed.
`saferemove-stepsize`::
Wipe step size in MiB (`blkdiscard -p` paramater value), capped to the maximum
step size supported by the underlying storage. Up to 32 MiB (maximum) by
default.
`saferemove_throughput`::