On 09/30/2013 02:37 PM, frank.gruellich@xxxxxxxx wrote:
Hi, I admit that my OSD IDs look rather strange: [osd.100660424296] host = xedwbnh296 dev = /dev/sdf [osd.110660424296] host = xedwbnh296 dev = /dev/sdg [osd.120660424296] host = xedwbnh296 dev = /dev/sdh [osd.130660424296] host = xedwbnh296 dev = /dev/sdi and of course ceph spills all kind of messages like 2013-09-30 13:07:01.649331 7f8218dd17a0 -1 must specify '-i #' where # is the osd number 2013-09-30 13:07:01.649339 7f8218dd17a0 -1 usage: ceph-osd -i osdid [--osd-data=path] [--osd-journal=path] [--mkfs] [--mkjournal] [--convert-filestore] 2013-09-30 13:07:01.649342 7f8218dd17a0 -1 --debug_osd N set debug level (e.g. 10) to me. It seems that my ID is too high. What's its limitation? And while we are on it, are there any limitations on mon and mds IDs? Thanks a lot in advance.
OSD IDs are incremental integers as spit out by the monitor when you create an osd ('ceph osd create <uuid>'). They're not free-form as you have with the monitor (and maybe the mds? not sure).
In any case, OSD ids are bound to range between 0 and 2^32-1, which is why you are getting that error message.
-Joao -- Joao Eduardo Luis Software Engineer | http://inktank.com | http://ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
