From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id A19101FF0C0 for ; Wed, 18 Nov 2026 18:30:46 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 68132216BA; Wed, 18 Nov 2026 18:30:46 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Kefu Chai Subject: applied: [PATCH pve-doc] pveceph: advise against using FastEC in production Date: Wed, 18 Nov 2026 18:30:28 +0100 Message-ID: <179502302445.1983063.6165802924277616297.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261104040501.2476504-1-k.chai@proxmox.com> References: <20261104040501.2476504-1-k.chai@proxmox.com> 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: 1795023036146 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.169 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: WXY3NXOS5VXP6PHB6QYBD257D4TFCEEV X-Message-ID-Hash: WXY3NXOS5VXP6PHB6QYBD257D4TFCEEV X-MailFrom: t.lamprecht@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: On Wed, 04 Nov 2026 12:05:01 +0800, Kefu Chai wrote: > The FastEC section reads as an endorsement and describes enabling the > flag on a populated pool as a change to pool metadata only. That does > not match what users have seen. Since Tentacle was released, FastEC has > hit several bugs [1][2][3][4][5], mostly around truncate, discard and > object size handling, and mostly on pools that already held data when > the flag was set. The symptoms range from bogus scrub errors, over > 'pg repair' making objects unfound, to OSDs crash-looping on their > first reconstruct read and taking the pool inactive. Some of the fixes > do not repair damage that was already done, and more fixes for > peering, recovery and the extent cache are still open upstream. > > [...] Applied, thanks! [1/1] pveceph: advise against using FastEC in production https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=205631e3110da3ac7f947b0b53d681e4f13be2ba