Ceph » RADOS

Is there a known workaround ?

Workaround suggested by Craig Lewis : recreate the OSDs that Ceph wants to probe. It doesn't have to have anything on it, it's probably better if it doesn't. Even ceph osd lost 2 won't help; Ceph won't mark the data lost until it's exhausted all possibilities.

I'm having a similar issue, I have one unfound object that I can't delete. I'm also getting the "Error EINVAL: pg has 32 objects but we haven't probed all sources, not marking lost" message.

Everything runs on 0.80.5

ceph pg 3.380 list_missing { "offset": { "oid": "",
"key": "",
"snapid": 0,
"hash": 0,
"max": 0,
"pool": -1,
"namespace": ""},
"num_missing": 1,
"num_unfound": 1,
"objects": [ { "oid": { "oid": "rbd_data.1982746cc8388.000000000000034c",
"key": "",
"snapid": -2,
"hash": 959071104,
"max": 0,
"pool": 3,
"namespace": ""},
"need": "3459'1083816",
"have": "3405'1083704",
"locations": []}],

While triggering "ceph pg 3.380 mark_unfound_lost revert", OSDs responsable for this object crash.

osdmap e5797 pool 'vms' (3) object 'rbd_data.1982746cc8388.000000000000034c' -> pg 3.392a4380 (3.380) -> up ([15,5,10], p15) acting ([1,6,9], p1)

OSD dump:
http://pastebin.com/QkwyStZM

@Samuel Just, I also met this problem, has this been solved ?

Hello,

I just had a customer facing this same issue, and to have it on the record, at least since luminous marking the OSD lost will work and you can mark_unfound_lost after.

So I assume you can close this ticket now!

Thank you,
best regards
Raimund Sacherer