From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES docs/storage 0/3] close #7204: document and check that thin pools have zeroing enabled
Date: Thu, 5 Feb 2026 17:38:03 +0100 [thread overview]
Message-ID: <20260205163819.219322-1-f.ebner@proxmox.com> (raw)
There were a bunch of new reports in the last week. Not sure why,
maybe a bogus tutorial out there or something along those lines.
Thin pools with zeroing during allocation turned off are currently not
supported for VM images. Using such a pool may lead to data
corruption for various operations like drive mirror.
Document this and add a check in the storage plugin upon storage
activation.
In the future, a dedicated storage configuration option could be
introduced that can be checked by volume_has_feature() and enforced
upon storage activation.
docs:
Fiona Ebner (1):
close #7204: storage: lvm thin: document that thin pools must have
zeroing enabled
pve-storage-lvmthin.adoc | 5 +++++
1 file changed, 5 insertions(+)
storage:
Fiona Ebner (2):
lvm plugin: list volumes: also query 'zero' property
close #7204: lvm thin plugin: die if thin pool does not have zeroing
configured
src/PVE/Storage/LVMPlugin.pm | 6 ++++--
src/PVE/Storage/LvmThinPlugin.pm | 17 ++++++++++++++++-
2 files changed, 20 insertions(+), 3 deletions(-)
Summary over all repositories:
3 files changed, 25 insertions(+), 3 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-02-05 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 16:38 Fiona Ebner [this message]
2026-02-05 16:38 ` [PATCH docs 1/3] close #7204: storage: lvm thin: document that thin pools must " Fiona Ebner
2026-02-05 16:38 ` [RFC storage 2/3] lvm plugin: list volumes: also query 'zero' property Fiona Ebner
2026-02-05 16:38 ` [RFC storage 3/3] close #7204: lvm thin plugin: die if thin pool does not have zeroing configured 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=20260205163819.219322-1-f.ebner@proxmox.com \
--to=f.ebner@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.