If you never ran "osd rm" then the monitors still believe it's an existing OSD. You can run that command after doing the crush rm stuff, but you should definitely do so.
On Friday, April 11, 2014, Chad Seys <cws...@physics.wisc.edu> wrote: > Hi Greg, > > How many monitors do you have? > > 1 . :) > > > It's also possible that re-used numbers won't get caught in this, > > depending on the process you went through to clean them up, but I > > don't remember the details of the code here. > > Yeah, too bad. I'm following the standard removal procedure in the URL > below, > except that instead of marking it out I just "crush remove" it as > suggested by > CERN (to avoid rebalancing twice): > https://ceph.com/docs/master/rados/operations/add-or-rm-osds/ > > I considered the "noin" command, but that would be global and I wouldn't > want > some transient outing of an OSD to domino as more an more OSDs become > active > to recover. > > Too bad there is not a "noin osdnum" command. > > One idea that might work is to record the new OSD's properties right after > creating it, then "ceph osd crush remove osd.osdnum". Later when all the > drives are added, "ceph osd crush add ...." them back. > > Any smoother way of doing this? Is there a crush move command that does > the > equivalent of crush rm ? ("ceph osd tree" makes it look like it got moved > out > of the tree. :) ) Any good way to get an OSD's vitals? "ceph osd crush > dump" > looks like it contains some info, but the weights are some kind of rescaled > integers... > > TTYL, > Chad. > -- Software Engineer #42 @ http://inktank.com | http://ceph.com
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
