Craig Chi
Is there a way to specify and OSD number on creation ? We run into situations where we have nodes that if the OSds are not created sequentially following the sda,sdb naming convention then the numbers are less than easy to correlate to hardware. In the example shown below we know OSD #341 has gone out. But it requires more research to find out what node and what drive are the issue. I know a UUID can be specified for the partition name but its not very helpful (Or i am using it wrong).
Apologies for not specifying version used or host OS as we are still in a pre deployment testing we are trying several versions from Hammer to jewel with different Debian and RHEL hosts to measure what fits best for our environment.
ID WEIGHT TYPE NAME UP/DOWN REWEIGHT PRIMARY-AFFINITY
-1 0 root default
0 0 osd.0 up 1.00000 1.00000
1 0 osd.1 up 1.00000 1.00000
2 0 osd.2 up 1.00000 1.00000
3 0 osd.3 up 1.00000 1.00000
4 0 osd.4 up 1.00000 1.00000
5 0 osd.5 up 1.00000 1.00000
6 0 osd.6 up 1.00000 1.00000~
334 0 osd.334 up 1.00000 1.00000
335 0 osd.335 up 1.00000 1.00000
336 0 osd.336 up 1.00000 1.00000
337 0 osd.337 up 1.00000 1.00000
338 0 osd.338 up 1.00000 1.00000
339 0 osd.339 up 1.00000 1.00000
340 0 osd.340 up 1.00000 1.00000
341 0 osd.341 down 0 1.00000
342 0 osd.342 up 1.00000 1.00000
343 0 osd.343 up 1.00000 1.00000
344 0 osd.344 up 1.00000 1.00000
345 0 osd.345 up 1.00000 1.00000
346 0 osd.346 up 1.00000 1.00000_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com