From: Stefan Priebe <s.priebe@profihost.ag>
To: Gregory Farnum <greg@inktank.com>
Cc: John Wilkins <john.wilkins@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph osd create XX
Date: Wed, 12 Dec 2012 23:00:55 +0100 [thread overview]
Message-ID: <50C8FE97.4020302@profihost.ag> (raw)
In-Reply-To: <CAPYLRzifpCB77z=YjbcxAPJ2TRF-NfH+MzgCbnGhFxrBLLs17Q@mail.gmail.com>
Hi Greg,
thanks for explanation. I'm using current next branch.
I'm using:
host1:
osd 11 .. 14
host2:
osd 21 .. 24
host3:
osd 31 .. 34
host4:
osd 41 .. 44
host5:
osd 51 .. 54
Right now i want to add host6. But i still don't know even with your
explanation how to add osd 61-64 to osdmap.
Greets Stefan
Am 12.12.2012 22:57, schrieb Gregory Farnum:
> On Wed, Dec 12, 2012 at 1:43 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> Hi Greg,
>>
>> i don't get it. I was using this doc:
>> http://ceph.com/docs/master/rados/operations/add-or-rm-osds/
>>
>> There is written that i have to use the osd-num for ceph osd create. Which
>> UUID is now meant?
>
> Ah, you're right — I don't think that doc has been correct since
> before argonaut, but prior to ~v0.55 it wouldn't complain on non-UUID
> values.
>
> The basic "ceph osd create" call simply allocates a new OSD ID and
> bumps the max allowed, and returns the new ID back to the caller. If
> you also specify the UUID, then it will check and see if that UUID
> already exists and simply return the allocated ID if it does
> (otherwise, create a new one as before). In argonaut, there's a bug
> that will silently ignore any non-UUID extra arguments, which is what
> was happening with those IDs.
>
> John, can you fix this in the docs please? :)
> -Greg
>
> (All this is assuming I've got my commit dates right; if not there
> might be a bit of variation about when which version took effect.)
>
>
>> I've already added osd.61,62,63 and 64 to ceph.conf
>>
>> Greets,
>> Stefan
>> Am 12.12.2012 22:41, schrieb Gregory Farnum:
>>>
>>> Yeah; 61 is not a valid UUID and you can't specify anything else on that
>>> line.
>>>
>>> On Wed, Dec 12, 2012 at 1:38 PM, Stefan Priebe <s.priebe@profihost.ag>
>>> wrote:
>>>>
>>>> HI Greg,
>>>>
>>>> sorry just a copy & paste error.
>>>>
>>>> [cloud1-ceph1: ~]# ceph osd create 61
>>>> (22) Invalid argument
>>>>
>>>>
>>>>> Read those two lines again. Very slowly. :)
>>>>>
>>>>> The correct syntax is
>>>>> ceph osd create <uuid>
>>>>>
>>>>> The uuid is optional, but you don't specify IDs; it gives you an ID
>>>>> back.
>>>>
>>>>
>>>>
>>>> Stefan
>>>
>>> --
>>>
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> 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@vger.kernel.org
> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-12-12 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 21:31 ceph osd create XX Stefan Priebe
2012-12-12 21:36 ` Gregory Farnum
2012-12-12 21:38 ` Stefan Priebe
2012-12-12 21:41 ` Gregory Farnum
2012-12-12 21:43 ` Stefan Priebe
2012-12-12 21:57 ` Gregory Farnum
2012-12-12 22:00 ` Stefan Priebe [this message]
2012-12-12 22:09 ` Gregory Farnum
2012-12-12 22:25 ` Stefan Priebe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C8FE97.4020302@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=john.wilkins@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox