Alert rule: CephPGNotDeepScrubbed

Please consider opening a PR to improve this runbook if you gain new information about causes of the alert, or how to debug or resolve the alert. Click "Edit this Page" in the top right corner to create a PR directly on GitHub.

Overview

One or more PGs haven’t been deep scrubbed recently. Deep scrubs protect against bit-rot. They compare data replicas to ensure consistency. When PGs miss their deep scrub interval, it may indicate that the window is too small or PGs weren’t in a clean state during the deep-scrub window.

Steps for debugging

Initiate a deep scrub

$ ceph_cluster_ns=syn-rook-ceph-cluster
$ kubectl -n ${ceph_cluster_ns} exec -it deploy/rook-ceph-tools -- ceph health detail
$ kubectl -n ${ceph_cluster_ns} exec -it deploy/rook-ceph-tools -- ceph pg deep-scrub <PG_ID_FROM_ALERT>

Upstream documentation

docs.ceph.com/en/latest/rados/operations/health-checks#pg-not-deep-scrubbed