On 10/13/25 13:44, Peter Grandi wrote:
On Mon, 13 Oct 2025 12:27:27 +0200, Sven Grottke <sfs@math.tu-berlin.de> said:
[...] but one of our pools is erasure-coded on 16TB HDDs.
This is the beginning of many sad stories :-).
The result of an unfortunate disconnect between a customer's requirements and their funding.
Two weeks ago, we upgraded from Reef to Squid (19.2.3) [...] an ever growing number of PGs that have not been deep-scrubbed or scrubbed in time. All these PGs are located on the HDD pool.
So far it is behaving as expected. Surprising that it did not happen before. Perhaps it started to become more fully used or to have more small files in that period of time.
It has been gradually filling up, so I suspect it's the former.
I would like to increase the scrubbing and deep-scrubbing intervals for the HDDs, but not for the SSDs. Is there any way to do that other than setting it on a per-OSD base [...]
The expectation for a significant Ceph setup is that its servers are managed by something like Ansible, CfEngine, etc, where configuration updates are distributed to many OSDs by that kind of tool. To some extent "orchestration" and GUI frontends can supplement that, but for finer control some kind of CM engine is usually needed.
We've been burnt in the past handing Ceph tuning over to Ansible. The solution Eugen suggested to set it on a per-pool base worked for us. Ciao, Sven
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io