Ceph 20.2 Tentacle Release Available as test preview and Ceph 18.2 Reef soon to be fully EOL

I`m tracking Ceph mailing list and from it I assume developers leaves testing stage to customers. Safe upgrade should be done to X.Y.2+ version only.
 
booodpoooq20 said:
just don't understand why they found this issue on Nov 4, 2025 but still released tentacle v20.2.0 on Nov 18, 2025
Click to expand...
I read it as only upgrades will have the issue due to padding ?

installing fresh with fastEC are not affected?

"The problem arises with "fast EC" for a pool which has been upgraded from a legacy EC pool. Any object that was written with legacy EC will be padded according to the legacy EC code, but scrubbing will check against the fast EC code, which pads shards more efficiently."
 
alexskysilk said:
I didnt know that, but that kinda begs the question what does the dashboard offer you beyond what PVE presents; if it really something necessary, I'd probably just set up ceph with cephadm seperate from pve. PVE doesnt consider the entirety of the ceph stack necessary for full function since it doesnt need all of it.
Click to expand...
We organice the automatic snapshots over the dashboard. So the cpehfs-mirror can mirror it to an other ceph cluster. Auto snapshot and mirror is not available in proxmox UI . And in the dashboard you can have a overview over the snapshots of the volumes.
 
If I understand correctly, the bug occurs if I enable the “allow_ec_optimizations” flag.
But if I upgrade from Squid without enabling this flag, everything should work normally, or am I wrong?
 
You must log in or register to reply here.
Top Bottom
Back