From: Alwin Antreich via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Alwin Antreich <alwin@antreich.com>
Subject: [pve-devel] [PATCH docs 2/2] pve-storage-lvm: add saferemove-stepsize
Date: Wed, 29 Oct 2025 14:27:45 +0100 [thread overview]
Message-ID: <mailman.373.1761744508.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <20251029132745.3127244-1-alwin@antreich.com>
[-- 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
next parent reply other threads:[~2025-10-29 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029132745.3127244-1-alwin@antreich.com>
2025-10-29 13:27 ` Alwin Antreich via pve-devel [this message]
2025-11-10 10:09 ` Alwin Antreich via pve-devel
2025-11-11 15:34 ` [pve-devel] applied: " Fiona Ebner
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=mailman.373.1761744508.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alwin@antreich.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.