So I'm not sure if this was the best or right way to do this but -- using rados I confirmed the unfound object was in the cephfs_data pool # rados -p cephfs_data ls|grep 001c0ed4
using the osdmap tool I found the pg/osd the unfound object was in -- # osdmaptool --test-map-object 10000000062.001c0ed4 osdmap (previously exported osdmap to file "osdmap") > object '10000000062.001c0ed4' -> 1.21 -> [4] then told ceph to just delete the unfound object ceph pg 1.21 mark_unfound_lost delete and then used rados to put the object back (from the file I had extracted previously) # rados -p cephfs_data put 10000000062.001c0ed4 10000000062.001c0ed4.obj Still have more recovery to do but this seems to have fixed my unfound object problem. On Tue, Jul 25, 2017 at 12:54 PM, Daniel K <satha...@gmail.com> wrote: > I did some bad things to my cluster, broke 5 OSDs and wound up with 1 > unfound object. > > I mounted one of the OSD drives, used ceph-objectstore-tool to find and > exported the object: > > ceph-objectstore-tool --data-path /var/lib/ceph/osd/ceph-10 > 10000000062.001c0ed4 get-bytes filename.obj > > > What's the best way to bring this object back into the active cluster? > > Do I need to bring an OSD offline, mount it and do the reverse of the > above command? > > Something like: > ceph-objectstore-tool --data-path /var/lib/ceph/osd/ceph-22 > 10000000062.001c0ed4 set-bytes filename.obj > > Is there some way to do this without bringing down an osd? > > > >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
