All of lore.kernel.org
 help / color / mirror / Atom feed
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:25:19 +0100	[thread overview]
Message-ID: <50C9044F.3000608@profihost.ag> (raw)
In-Reply-To: <CAPYLRzhq2DMvRoLPsEG0FJ-AejwQ7KyjhZs8iwZbEtecUpA6Ug@mail.gmail.com>

ah OK good to know.

UUIDs are a good decision but right now the journal devices (if you use 
a block device) are still absolute.

[osd.23]
         host = cloud1-ceph2
         public addr = 10.255.0.101
         cluster addr = 10.255.0.101
         osd journal  = /dev/sdd1

Greets,
Stefan

Am 12.12.2012 23:09, schrieb Gregory Farnum:
> On Wed, Dec 12, 2012 at 2:00 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> 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.
>
> Yeah, it's not going to let you allocate non-sequential IDs at this
> point, sorry. We are slowly divorcing the ID and the name, but it's
> not done yet...
>

      reply	other threads:[~2012-12-12 22:25 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
2012-12-12 22:09             ` Gregory Farnum
2012-12-12 22:25               ` Stefan Priebe [this message]

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=50C9044F.3000608@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.