From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 3BDDA1FF13C for ; Thu, 05 Feb 2026 17:38:23 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6524D16B05; Thu, 5 Feb 2026 17:38:56 +0100 (CET) From: Fiona Ebner 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 Message-ID: <20260205163819.219322-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770309425185 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.017 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: KCPYN2IXFIXZD4QLHACP3VLN6CMOQ75W X-Message-ID-Hash: KCPYN2IXFIXZD4QLHACP3VLN6CMOQ75W X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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