From: Dimitri Maziuk <dmaziuk@bmrb.wisc.edu>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Understanding Ceph
Date: Thu, 24 Jan 2013 07:55:43 -0600 [thread overview]
Message-ID: <51013D5F.7090105@bmrb.wisc.edu> (raw)
In-Reply-To: <CAJH6TXhwBY+gTDDksCfMroDodeN1b8ttM7zjNc2tn5PXzYbcZg@mail.gmail.com>
On 1/24/2013 2:49 AM, Gandalf Corvotempesta wrote:
> 2013/1/24 Dimitri Maziuk <dmaziuk@bmrb.wisc.edu>:
>> So I'm stuck at a point way before those guides become relevant: once I
>> had one OSD/MDS/MON box up, I got "HEALTH_WARN 384 pgs degraded; 384 pgs
>> stuck unclean; recovery 21/42 degraded (50.000%)" (384 appears be the
>> number of placement groups created by default).
>>
>> What does that mean? That I only have one OSD? Or is it genuinely unhealthy?
>
> ceph is building it's cluster. You should wait for it.
> In my case, it needed 5-10 minutes.
No, that's not it: it was stuck in that state for 40 minutes or so.
Dima
next prev parent reply other threads:[~2013-01-24 13:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 15:50 Understanding Ceph Peter Smith
2013-01-19 16:26 ` Dimitri Maziuk
2013-01-19 16:51 ` Denis Fondras
2013-01-19 17:15 ` Wenhao Xu
2013-01-19 17:13 ` Sage Weil
2013-01-19 17:25 ` Peter Smith
2013-01-19 17:38 ` Sage Weil
2013-01-19 18:08 ` Jeff Mitchell
2013-01-19 18:16 ` Sage Weil
2013-01-19 18:25 ` Peter Smith
2013-01-20 16:39 ` Dimitri Maziuk
2013-01-23 15:13 ` Sam Lang
2013-01-23 16:19 ` Patrick McGarry
2013-01-24 0:10 ` Dimitri Maziuk
2013-01-24 0:17 ` John Nielsen
2013-01-24 2:36 ` Dimitri Maziuk
2013-01-24 15:45 ` Dimitri Maziuk
2013-01-24 15:53 ` Jens Kristian Søgaard
2013-01-24 15:58 ` Wido den Hollander
2013-01-24 16:14 ` Dimitri Maziuk
2013-01-24 16:18 ` Jens Kristian Søgaard
2013-01-24 16:22 ` Sam Lang
2013-01-24 17:09 ` Dimitri Maziuk
2013-01-24 17:16 ` John Nielsen
2013-01-24 8:49 ` Gandalf Corvotempesta
2013-01-24 13:55 ` Dimitri Maziuk [this message]
[not found] ` <CAKMAVE9HMo4x3seuG7ppeafSRJmBwjUXrLv0GUA-z5kDXyhoQA@mail.gmail.com>
2013-01-24 15:28 ` Dimitri Maziuk
2013-01-24 16:12 ` Sam Lang
2013-01-24 18:15 ` Dan Mick
2013-01-24 18:58 ` Dimitri Maziuk
2013-01-24 21:07 ` Dan Mick
2013-01-24 21:45 ` Dimitri Maziuk
2013-01-24 21:48 ` Sage Weil
2013-01-24 21:51 ` Dimitri Maziuk
[not found] ` <CAM2gkg6 m2S0DtgapSOg16GTmGQHsj7fz=a3XzH0ZsvcCWHcBtg@mail.gmail.com>
[not found] ` <CAM2gkg6m2S0DtgapSOg16GTmGQHsj7fz=a3XzH0ZsvcCWHcBtg@mail.gmail.com>
2013-01-24 19:52 ` Dimitri Maziuk
2013-01-24 20:53 ` John Wilkins
2013-01-24 22:15 ` Dimitri Maziuk
2013-01-24 22:52 ` Josh Durgin
2013-01-24 23:36 ` John Wilkins
2013-01-24 23:38 ` Josh Durgin
2013-01-19 18:16 ` Peter Smith
2013-01-19 21:10 ` Josh Durgin
2013-01-20 0:41 ` Jeff Mitchell
2013-01-20 3:24 ` Peter Smith
2013-01-20 3:56 ` Sage Weil
2013-01-20 16:32 ` Dimitri Maziuk
2013-01-24 18:16 ` Dan Mick
2013-01-24 20:14 ` Dimitri Maziuk
-- strict thread matches above, loose matches on Subject: below --
2011-12-18 6:41 Bill Hastings
2011-12-18 12:17 ` Christian Brunner
2011-12-18 16:43 ` Bill Hastings
2011-12-18 17:17 ` Yehuda Sadeh Weinraub
2011-12-18 17:37 ` Bill Hastings
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=51013D5F.7090105@bmrb.wisc.edu \
--to=dmaziuk@bmrb.wisc.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=gandalf.corvotempesta@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.