If you're describing what I think you are, I should think ceph osd CRUSH remove osd.1701 without an associated ceph osd rm would do it. Be sure to follow with `auth del` when done. > > Several years ago the ceph osd tree command could return OSDs in a > 'stray' state and the OSDs could stay in that state indefinitely until > the underlying issues with the backing drive or OSD process were > resolved, or the OSD was removed. It used to be that I could force > this state by blowing away a backing OSD drive out from under CEPH. > The recipe I used to do this no longer works. I have written code that > looks at the output of ceph osd tree and accounts for the 'stray' > state. Now I need to modify this code, but I can no longer get an OSD > into this persistent 'stray' state. > > Is there any possibility with Jewel or Luminous that an OSD can be in > a persistent stray state? > > If so, how can I produce this state? > > Sincerely, > > Jeff McManus > Keeper Technology > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
