From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Removing disks / OSDs
Date: Wed, 23 Oct 2013 08:29:43 +0200 [thread overview]
Message-ID: <52676CD7.50509@dachary.org> (raw)
In-Reply-To: <CAPYLRzgxWEi1s0=-EtcbhpdS8H96KDm-NhxhScKOn18Y72DY5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
On 22/10/2013 19:26, Gregory Farnum wrote:
> On Mon, Oct 21, 2013 at 11:13 PM, Loic Dachary <loic@dachary.org> wrote:
>>
>>
>> On 21/10/2013 18:49, Gregory Farnum wrote:
>>> I'm not quite sure what questions you're actually asking here...
>>> In general, the OSD is not removed from the system without explicit
>>> admin intervention. When it is removed, all traces of it should be
>>> zapped (including its key), so it can't reconnect.
>>> If it hasn't been removed, then indeed it will continue working
>>> properly even if moved to a different box.
>>
>> If there is an external journal, the device containing the journal needs to be moved with the device containing the data. If I read ceph/src/upstart/ceph-osd.conf correctly, when the data device is plugged in the new machine it will fail to start because the journal is not there yet. When the journal device is plugged in, the ceph-osd.conf would be called because udev rule in ceph/udev/95-ceph-osd.rules call ceph-disk activate-journal.
>>
>> Is my understanding correct ?
>
> Well, after being wrong last time I'm a little reluctant to make
> pronouncements from memory, but that definitely sounds correct to me.
> :) If I were doing an audit I'd want to look at what happens if there
> is a wrong journal in the correct location, etc.
Thanks. It makes things real simple from the configuration point of view :-)
Cheers
> -Greg
> Software Engineer #42 @ http://inktank.com | http://ceph.com
>
--
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-10-23 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 16:15 Removing disks / OSDs Loic Dachary
2013-10-21 16:49 ` Gregory Farnum
2013-10-21 16:57 ` Loic Dachary
2013-10-21 17:17 ` Gregory Farnum
2013-10-21 21:15 ` Mark Kirkwood
2013-10-22 6:13 ` Loic Dachary
2013-10-22 17:26 ` Gregory Farnum
2013-10-22 17:31 ` Sage Weil
2013-10-23 13:45 ` Loic Dachary
2013-10-25 13:11 ` Loic Dachary
2013-10-25 15:58 ` Sage Weil
2013-10-23 6:29 ` Loic Dachary [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=52676CD7.50509@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@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.