From: "Łukasz Chrustek" <skidoo@tlen.pl>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Problem with query and any operation on PGs
Date: Tue, 23 May 2017 23:43:31 +0200 [thread overview]
Message-ID: <1075363645.20170523234331@tlen.pl> (raw)
In-Reply-To: <alpine.DEB.2.11.1705231738520.3646@piezo.novalocal>
Cześć,
> On Tue, 23 May 2017, Łukasz Chrustek wrote:
>> I'm not sleeping for over 30 hours, and still can't find solution. I
>> did, as You wrote, but turning off this
>> (https://pastebin.com/1npBXeMV) osds didn't resolve issue...
> The important bit is:
> "blocked": "peering is blocked due to down osds",
> "down_osds_we_would_probe": [
> 6,
> 10,
> 33,
> 37,
> 72
> ],
> "peering_blocked_by": [
> {
> "osd": 6,
> "current_lost_at": 0,
> "comment": "starting or marking this osd lost may let
> us proceed"
> },
> {
> "osd": 10,
> "current_lost_at": 0,
> "comment": "starting or marking this osd lost may let
> us proceed"
> },
> {
> "osd": 37,
> "current_lost_at": 0,
> "comment": "starting or marking this osd lost may let
> us proceed"
> },
> {
> "osd": 72,
> "current_lost_at": 113771,
> "comment": "starting or marking this osd lost may let
> us proceed"
> }
> ]
> },
> Are any of those OSDs startable?
They were all up and running - but I decided to shut them down and out
them from ceph, now it looks like ceph working ok, but still two PGs
are in down state, how to get rid of it ?
ceph health detail
HEALTH_WARN 2 pgs down; 2 pgs peering; 2 pgs stuck inactive
pg 1.165 is stuck inactive since forever, current state down+remapped+peering, last acting [38,48]
pg 1.60 is stuck inactive since forever, current state down+remapped+peering, last acting [66,40]
pg 1.60 is down+remapped+peering, acting [66,40]
pg 1.165 is down+remapped+peering, acting [38,48]
[root@cc1 ~]# ceph -s
cluster 8cdfbff9-b7be-46de-85bd-9d49866fcf60
health HEALTH_WARN
2 pgs down
2 pgs peering
2 pgs stuck inactive
monmap e1: 3 mons at {cc1=192.168.128.1:6789/0,cc2=192.168.128.2:6789/0,cc3=192.168.128.3:6789/0}
election epoch 872, quorum 0,1,2 cc1,cc2,cc3
osdmap e115175: 100 osds: 88 up, 86 in; 2 remapped pgs
pgmap v67583069: 3520 pgs, 17 pools, 26675 GB data, 4849 kobjects
76638 GB used, 107 TB / 182 TB avail
3515 active+clean
3 active+clean+scrubbing+deep
2 down+remapped+peering
client io 0 B/s rd, 869 kB/s wr, 14 op/s rd, 113 op/s wr
--
Regards
Łukasz Chrustek
next prev parent reply other threads:[~2017-05-23 21:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175484591.20170523135449@tlen.pl>
2017-05-23 12:48 ` Problem with query and any operation on PGs Łukasz Chrustek
2017-05-23 14:17 ` Sage Weil
2017-05-23 14:43 ` Łukasz Chrustek
[not found] ` <1464688590.20170523185052@tlen.pl>
2017-05-23 17:40 ` Sage Weil
2017-05-23 21:43 ` Łukasz Chrustek [this message]
2017-05-23 21:48 ` Sage Weil
2017-05-24 13:19 ` Łukasz Chrustek
2017-05-24 13:37 ` Sage Weil
2017-05-24 13:58 ` Łukasz Chrustek
2017-05-24 14:02 ` Sage Weil
2017-05-24 14:18 ` Łukasz Chrustek
2017-05-24 14:47 ` Sage Weil
2017-05-24 15:00 ` Łukasz Chrustek
2017-05-24 15:07 ` Łukasz Chrustek
2017-05-24 15:11 ` Sage Weil
2017-05-24 15:24 ` Łukasz Chrustek
2017-05-24 15:54 ` Łukasz Chrustek
2017-05-24 16:02 ` Łukasz Chrustek
2017-05-24 17:07 ` Łukasz Chrustek
2017-05-24 17:16 ` Sage Weil
2017-05-24 17:28 ` Łukasz Chrustek
2017-05-24 18:16 ` Sage Weil
2017-05-24 19:47 ` Łukasz Chrustek
2017-05-24 17:30 ` Łukasz Chrustek
2017-05-24 17:35 ` Łukasz Chrustek
2017-05-24 21:38 ` Łukasz Chrustek
2017-05-24 21:53 ` Sage Weil
2017-05-24 22:09 ` Łukasz Chrustek
2017-05-24 22:27 ` Sage Weil
2017-05-24 22:46 ` Łukasz Chrustek
2017-05-25 2:06 ` Sage Weil
2017-05-25 11:22 ` Łukasz Chrustek
2017-05-29 15:31 ` Łukasz Chrustek
2017-05-30 13:21 ` Sage Weil
2017-06-10 22:45 ` Łukasz Chrustek
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=1075363645.20170523234331@tlen.pl \
--to=skidoo@tlen.pl \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.