From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Subject: applied: [PATCH pve-doc] pveceph: advise against using FastEC in production
Date: Wed, 18 Nov 2026 18:30:28 +0100 [thread overview]
Message-ID: <179502302445.1983063.6165802924277616297.b4-ty@b4> (raw)
In-Reply-To: <20261104040501.2476504-1-k.chai@proxmox.com>
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
prev parent reply other threads:[~2026-11-18 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 4:05 [PATCH pve-doc] pveceph: advise against using FastEC in production Kefu Chai
2026-11-04 14:51 ` Laurențiu Leahu-Vlăducu
2026-11-18 17:30 ` Thomas Lamprecht [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=179502302445.1983063.6165802924277616297.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=k.chai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox