On Wed, Jul 11, 2018 at 8:07 AM Flash <flashick@xxxxxxxxx> wrote:
Hi there.Yesterday I caught that error:PG_DAMAGED Possible data damage: 2 pgs snaptrim_errorpg 11.9 is active+clean+snaptrim_error, acting [196,167,32]pg 11.127 is active+clean+snaptrim_error, acting [184,138,1]May it be because the scrub was done when the snapshots were cleaned up?
Hmm, the only way you can get the snaptrim_error state is if the PG gets an error when it tries to trim a particular snapshotted object. And it doesn't get cleared by scrubbing; only when it starts snaptrimming again.
If you have any OSD logs of when this happened, that would be helpful.
And, uh, Sage? Do you know what was supposed to happen here? It's a bit odd as a PG state.
-Greg
_______________________________________________I tried to restart OSD, then I run deep-scrub and repair, but it didn't solve the problem.In the documentation the page "Repairing PG inconsistencies" is empty - http://docs.ceph.com/docs/mimic/rados/operations/pg-repair/,so I don't know, what else can I do?Cluster info;vaersion 12.2.525 OSD nodes12 OSD per node. The most of them still have filestore as storage backend.
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
