From: Wido den Hollander <wido@widodh.nl>
To: Marco Aroldi <marco.aroldi@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Failed HD, automate procedure?
Date: Mon, 02 Apr 2012 17:07:07 +0200 [thread overview]
Message-ID: <4F79C09B.2040902@widodh.nl> (raw)
In-Reply-To: <CAHzdKU+85+aKqr2aQqCcrnzjo4kou3FVQxCLAZpa=OKN_ZNfOw@mail.gmail.com>
Hi,
On 04/02/2012 12:31 PM, Marco Aroldi wrote:
> Hi all,
> i'm looking the procedure to replace a failed HD
> (http://ceph.newdream.net/wiki/Replacing_a_failed_disk/OSD)
The Wiki is a bit outdated, most of the docs are moving to
http://ceph.newdream.net/docs/ but the Wiki is still linked on the
frontpage.
> and I was wondering if the procedure could be more automated like:
>
> 1- The operator replaces the failed hd, say osd.23
> 2- Give a new command like "ceph reborn osd.23"
Currently that isn't available. But some discussion has been going on
about this: http://marc.info/?l=ceph-devel&m=133106885906229&w=2
That might not seem related at first glance, but it is. Somehow that new
disk has to be formatted and linked to the new OSD.
A OSD simply wants a data directory were to store it's data.
If you replace the disk, something/somebody has to format that disk and
make sure it's mounted.
When that's done, the OSD can format the fresh data directory and
connect to the cluster again.
The OSD also needs the current monitor map and needs his key to
authenticate to the cluster.
That data needs to come from somewhere, some form of external
involvement is needed to get this done.
To make the story short: This is on the radar.
Wido
>
> Thanks, thanks to all the community for this big piece of software!
> Marco Aroldi
> --
> 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-04-02 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 10:31 Failed HD, automate procedure? Marco Aroldi
2012-04-02 15:07 ` Wido den Hollander [this message]
2012-04-02 16:23 ` Tommi Virtanen
2012-04-02 20:33 ` Marco Aroldi
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=4F79C09B.2040902@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=marco.aroldi@gmail.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.