-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I have a 0.94.4 cluster that when I repair/deep-scrub a PG, it comes back clean, but as soon as I restart any OSD that hosts it, it goes back to inconsistent. If I deep-scrub that PG it clears up. I determined that the bad copy was not on the primary and issued a pg repair command. I have shut down and deleted the PG folder on each OSD in turn and let it back fill. I tried taking the primary OSD down and issuing a repair command then. I took an m5sum of all files in the PG directory and compared all files across the OSDs and it came back clean. I shut down each OSD in turn and removed any PG_TEMP directories. I'm just not sure why the cluster is so confused as to the status of this PG. Any ideas? - ---------------- Robert LeBlanc PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1 -----BEGIN PGP SIGNATURE----- Version: Mailvelope v1.2.2 Comment: https://www.mailvelope.com wsFcBAEBCAAQBQJWLWr3CRDmVDuy+mK58QAA4HEP/361NhUXujdrKr9xa4d/ Lr/zMCbppT7uof3BueLkkIF2erun19ENNLZV5ehyzcbeWlHVA3UEzJaZlaew eQrmFN0TKk2BFtQAnXp66KhBVco05tiLKZthkGH9AzwQT33ftf8ErVwT4GXs aEXDdQLctLGxvqfoyys9woNqalYjG9JtZxJHTWfaVU+t3yXEme3GBJBmMlVE GSSk8KAyEil8DP1q4PMQJrScQxqYFpfBi1UGnbiQj02pan16OtbkaUkJNLMB o8XlHdiNfPWmMoyAuOPBMoKSPo1diLBP3uEJN8u3Mw4+9kLZSeMDMRHdkMF0 kmhGA26ihRHcHWVsC+4wevCGJoq7vvPmf8892z+hEjC5vm4eWGAD7UPBjqjl 5BL282XI+AYLbw4VkiDrP4tTL4neOr6IW50mnG8SPVSAvMN+cFJnlMZRpQ/6 SQB4Tv5fr1SEMZDZqC//RacWZYCsBd1XZi6M0VhOhOrGjqmlr/41P2dmrdI1 ldHEyl3l07mJdBANQ0AgIMAeMyuD3dGQ4q0IpJgVMbrfxq8m/lLp/jddOWq3 MhNGT5J1K4Qg3eFlqhuTIw7yLmERACYHlMUBCHGq/8jGCjEQOe6uhuePyH/6 ugUoZ+J4Y+Fxsu1Jsoj+GQtDSSkOTGjUpGhXPp/gqMhxZRlGdsZL5LIEs7hm Us8M =gnRK -----END PGP SIGNATURE----- _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |