Hello,
'ceph osd deep-scrub 5' deep-scrubs all PGs for which osd.5 is primary (and only those).
You can check that from ceph-osd.5.log by running:
for pg in $(grep 'deep-scrub starts' /var/log/ceph/*/ceph-osd.5.log | awk '{print $8}') ; do echo "pg: $pg, primary osd is osd.$(ceph pg $pg query -f json | jq '.info.stats.acting_primary')" ; done
while
'ceph osd deep-scrub all' instructs all OSDs to start deep-scrubbing all PGs they're primary for, so in the end, all cluster's PGs.
So if the data you overwrote on osd.5 with 'dd' was part of a PG for which osd.5 was not the primary OSD then it wasn't deep-scrubbed.
man ceph 8 could rather say:
Subcommand deep-scrub initiates deep scrub on all PGs osd <who> is primary for.
Usage:
ceph osd deep-scrub <who>
Regards,
Frédéric.
----- Le 10 Juin 24, à 16:51, Petr Bena petr@bena.rocks a écrit :
> Most likely it wasn't, the ceph help or documentation is not very clear about
> this:
>
> osd deep-scrub <who>
> initiate
> deep scrub on osd <who>, or use <all|any> to deep scrub all
>
> It doesn't say anything like "initiate deep scrub of primary PGs on osd"
>
> I assumed it just runs a scrub of everything on given OSD.
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
