Hi,
On 08/23/2016 08:19 PM, Reed Dier wrote:
Trying to hunt down a mystery osd populated in the osd tree.
Cluster was deployed using ceph-deploy on an admin node, originally 10.2.1 at time of deployment, but since upgraded to 10.2.2.
For reference, mons and mds do not live on the osd nodes, and the admin node is neither mon, mds, or osd.
Attempting to remove it from the crush map, it says that osd.0 does not exist.
Just looking for some insight into this mystery.
Thanks
# ceph osd tree
ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY
-1 58.19960 root default
-2 7.27489 host node24
1 7.27489 osd.1 up 1.00000 1.00000
-3 7.27489 host node25
2 7.27489 osd.2 up 1.00000 1.00000
-4 7.27489 host node26
3 7.27489 osd.3 up 1.00000 1.00000
-5 7.27489 host node27
4 7.27489 osd.4 up 1.00000 1.00000
-6 7.27489 host node28
5 7.27489 osd.5 up 1.00000 1.00000
-7 7.27489 host node29
6 7.27489 osd.6 up 1.00000 1.00000
-8 7.27539 host node30
9 7.27539 osd.9 up 1.00000 1.00000
-9 7.27489 host node31
7 7.27489 osd.7 up 1.00000 1.00000
0 0 osd.0 down 0 1.00000
I've seen these entries during manual removal of OSD. There's still an
OSD entry, but no crush location (e.g. after 'ceph osd crush remove ..'
and before 'ceph osd rm ...'). It also happens if you invoke ceph-osd
manually to create an OSD entry.
You should be able to remove this entry with 'ceph osd rm 0'.
Regards,
Burkhard
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
