From: Stefan Priebe <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph stays degraded after crushmap rearrangement
Date: Sat, 05 Jan 2013 18:03:05 +0100 [thread overview]
Message-ID: <50E85CC9.9080503@profihost.ag> (raw)
In-Reply-To: <50E85799.4060607@profihost.ag>
Hello,
now i cannot even access an rbd image anymore.
Hanging status is now:
2013-01-05 18:01:21.736298 mon.0 [INF] pgmap v2212193: 7632 pgs: 1
stale, 10 peering, 14 stale+peering, 1 stale+remapped, 1807
stale+active+remapped, 1 stale+active+degraded, 2587 remapped+peering,
1767 stale+remapped+peering, 1341 stale+active+degraded+remapped, 103
stale+active+replay+degraded+remapped; 152 GB data, 313 GB used, 5022 GB
/ 5336 GB avail; 7647/79122 degraded (9.665%)
Stefan
Am 05.01.2013 17:40, schrieb Stefan Priebe:
> Hi list,
>
> i've rearranged my crushmap. Ceph was degraded about 18% and was
> recovering / rearranging fine.
>
> But now it stays still and degraded status is rising??
>
> 2013-01-05 17:35:40.906587 mon.0 [INF] pgmap v2211269: 7632 pgs: 7632
> active+remapped; 152 GB data, 312 GB used, 5023 GB / 5336 GB avail;
> 22/79086 degraded (0.028%)
>
> ...
>
> 2013-01-05 17:37:50.142106 mon.0 [INF] pgmap v2211386: 7632 pgs: 7632
> active+remapped; 152 GB data, 312 GB used, 5023 GB / 5336 GB avail;
> 24/79090 degraded (0.030%)
>
> ..
>
> 2013-01-05 17:40:35.292054 mon.0 [INF] pgmap v2211526: 7632 pgs: 7632
> active+remapped; 152 GB data, 313 GB used, 5023 GB / 5336 GB avail;
> 32/79106 degraded (0.040%)
>
> I'm on currect testing branch.
>
> Greets,
> Stefan
next prev parent reply other threads:[~2013-01-05 17:03 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 [this message]
2013-01-05 17:06 ` Sage Weil
2013-01-05 17:11 ` Stefan Priebe
2013-01-05 17:16 ` Stefan Priebe
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=50E85CC9.9080503@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
/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.