All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph stays degraded after crushmap rearrangement
Date: Sat, 05 Jan 2013 18:16:56 +0100	[thread overview]
Message-ID: <50E86008.30000@profihost.ag> (raw)
In-Reply-To: <50E85EB1.8060803@profihost.ag>

Hi,
Am 05.01.2013 18:11, schrieb Stefan Priebe:
> Hi,
>
> i just stopped EVERYTHING and have now started ALL osds again. It seems
> to recover now. But here is the output.
Just an illusion. Still hangs.

# ceph -s
    health HEALTH_WARN 934 pgs degraded; 23 pgs down; 1887 pgs peering; 
1330 pgs stale; 670 pgs stuck inactive; 882 pgs stuck stale; 7632 pgs 
stuck unclean; recovery 4811/79122 degraded (6.080%)
    monmap e1: 3 mons at 
{a=10.255.0.100:6789/0,b=10.255.0.101:6789/0,c=10.255.0.102:6789/0}, 
election epoch 1996, quorum 0,1,2 a,b,c
    osdmap e8393: 24 osds: 24 up, 24 in
     pgmap v2212487: 7632 pgs: 475 peering, 4013 active+remapped, 18 
down+peering, 490 active+degraded, 798 stale+active+remapped, 1 
active+replay+degraded, 1305 remapped+peering, 84 
stale+remapped+peering, 5 stale+down+remapped+peering, 364 
stale+active+degraded+remapped, 79 
stale+active+replay+degraded+remapped; 152 GB data, 314 GB used, 5021 GB 
/ 5336 GB avail; 4811/79122 degraded (6.080%)
    mdsmap e1: 0/0/1 up

Greets,
Stefan

  reply	other threads:[~2013-01-05 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 16:40 ceph stays degraded after crushmap rearrangement Stefan Priebe
2013-01-05 17:03 ` Stefan Priebe
2013-01-05 17:06   ` Sage Weil
2013-01-05 17:11     ` Stefan Priebe
2013-01-05 17:16       ` Stefan Priebe [this message]
2013-01-05 17:40         ` Sage Weil
2013-01-05 17:46           ` Stefan Priebe
2013-01-05 17:56             ` Sage Weil
2013-01-05 18:05               ` Stefan Priebe
2013-01-05 18:15                 ` Stefan Priebe
2013-01-05 18:46                 ` Sage Weil

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=50E86008.30000@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@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.