Hey,
I have a PG that after a deep-scrub it shows the following output:
3.0 deep-scrub : stat mismatch, got 23/24 objects, 0/0 clones, 23/24 dirty, 23/24 omap, 0/0 pinned, 0/0 hit_set_archive, 0/0 whiteouts, 0/0 bytes, 0/0 manifest objects, 0/0 hit_set_archive bytes.
This is on a metadata pool on SSD's.
If I run another deep-scrub it never starts, if I restart the primary OSD the error goes away till a few days later when it run's another scrub (i guess), is there a simple/safe way I can fix this.
I want to check before I just go and run a PG repair, that a repair is the correct / best option.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
