With BlueStore, all data is checksumed by default, so the steps in this section to safely determine the correct copy of the object no longer apply.
We will now see how we can correctly repair inconsistent objects:
- To be able to recreate an inconsistent scenario, create an RBD, and later we'll make a filesystem on it:
- Check to see which objects have been created by formatting the RBD with a filesystem:
- Pick one object at random and use the osd map command to find out which PG the object is stored in:
- Find this object on the disk on one of the OSD nodes; in this case, it is OSD.0 on OSD1:
- Corrupt it by echoing garbage over the top of it:
- Tell Ceph to do a scrub on the PG that contains the object we corrupted:
- If you check the Ceph status, you will see that Ceph has detected the corrupted object and marked the PG as inconsistent...
