Bug #41318
Updated by Sage Weil over 4 years ago
- recovery creates a temp recovery object,
<pre>
2019-08-15T22:50:41.202+0000 7f30cc74b700 15 bluestore(/var/lib/ceph/osd/ceph-2) _omap_setkeys 9.0_head #-11:05876d40:::temp_recovering_9.0_45'8_50_head:head#
2019-08-15T22:50:41.202+0000 7f30cc74b700 20 bluestore(/var/lib/ceph/osd/ceph-2) _omap_setkeys 0xfffffffffffffff500000000000005ed'.foo0' <- foo0
2019-08-15T22:50:41.202+0000 7f30cc74b700 20 bluestore(/var/lib/ceph/osd/ceph-2) _omap_setkeys 0xfffffffffffffff500000000000005ed'.foo1' <- foo1
2019-08-15T22:50:41.202+0000 7f30cc74b700 20 bluestore(/var/lib/ceph/osd/ceph-2) _omap_setkeys 0xfffffffffffffff500000000000005ed'.foo10' <- foo10
2019-08-15T22:50:41.202+0000 7f30cc74b700 20 bluestore(/var/lib/ceph/osd/ceph-2) _omap_setkeys 0xfffffffffffffff500000000000005ed'.foo100' <- foo100
</pre>
- it gets renamed,
<pre>
2019-08-15T22:50:41.394+0000 7f30cc74b700 10 bluestore(/var/lib/ceph/osd/ceph-2) _rename 9.0_head #-11:05876d40:::temp_recovering_9.0_45'8_50_head:head# -> #9:05876d40:test-rados-api-smithi104-15134-17::big2:head# = 0
</pre>
- now the pool id is different, so we won't find hte omap data. for example, on removal,
<pre>
2019-08-15T22:51:42.487+0000 7f30d0753700 20 bluestore(/var/lib/ceph/osd/ceph-2) _do_omap_clear remove range start: 0x000000000000000900000000000006b2'-' end: 0x000000000000000900000000000006b2'~'
</pre>
/a/sage-2019-08-15_21:25:02-rados-wip-sage-testing-2019-08-15-1347-distro-basic-smithi/4217741