From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/1] storage: lvm: expand on description of saferemove option
Date: Tue, 09 Jan 2024 10:38:24 +0100 [thread overview]
Message-ID: <1704793089.szo3720zta.astroid@yuna.none> (raw)
In-Reply-To: <20231207161038.90626-3-f.ebner@proxmox.com>
On December 7, 2023 5:10 pm, Fiona Ebner wrote:
> mentioning why zeroing-out might be necessary.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> pve-storage-lvm.adoc | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc
> index 917d8fb..cff5d3e 100644
> --- a/pve-storage-lvm.adoc
> +++ b/pve-storage-lvm.adoc
> @@ -38,7 +38,10 @@ on a remote iSCSI server.
> `saferemove`::
>
> Zero-out data when removing LVs. When removing a volume, this makes
> -sure that all data gets erased.
> +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.
>
> `saferemove_throughput`::
>
> --
> 2.39.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
>
prev parent reply other threads:[~2024-01-09 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:10 [pve-devel] [RFC manager/docs] lvm: better expose/explain " Fiona Ebner
2023-12-07 16:10 ` [pve-devel] [RFC manager 1/1] ui: lvm: expose saferemove setting Fiona Ebner
2024-01-09 9:49 ` Fabian Grünbichler
2023-12-07 16:10 ` [pve-devel] [PATCH docs 1/1] storage: lvm: expand on description of saferemove option Fiona Ebner
2024-01-09 9:38 ` Fabian Grünbichler [this message]
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=1704793089.szo3720zta.astroid@yuna.none \
--to=f.gruenbichler@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 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.