From: "Łukasz Chrustek" <skidoo@tlen.pl>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: problem with removing osd
Date: Thu, 29 Dec 2016 21:55:18 +0100 [thread overview]
Message-ID: <1039341611.20161229215518@tlen.pl> (raw)
In-Reply-To: <alpine.DEB.2.11.1612292048580.10615@piezo.novalocal>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Cześć,
>> >>
>> >> here i press ctrl+c
>> >>
>> >> 2016-12-28 17:38:10.055239 7f4576d7a700 0 monclient: hunting for new mon
>> >> 2016-12-28 17:38:10.055582 7f4574233700 0 -- 192.168.128.1:0/1201679761 >> 192.168.128.2:6789/0 pipe(0x7f456c023190 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7f456c024470).fault
>> >> 2016-12-28 17:38:30.550622 7f4574233700 0 -- 192.168.128.1:0/1201679761 >> 192.168.128.1:6789/0 pipe(0x7f45600008c0 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7f4560001df0).fault
>> >> 2016-12-28 17:38:54.551031 7f4574474700 0 -- 192.168.128.1:0/1201679761 >> 192.168.128.2:6789/0 pipe(0x7f45600046c0 sd=4 :0 s=1 pgs=0 cs=0 l=1 c=0x7f45600042b0).fault
>>
>> > What version is this?
>>
>> infernalis
>>
>> > Can you attach the crush map too? (ceph osd crush dump -f json-pretty)
>>
>> I can't - ceph-mons are crushing on diffrent ceph-mon hosts:
>>
>> ]# ceph osd crush dump -f json-pretty
> Hmm, in that case, 'ceph osd getcrushmap -o cm' and post that somewhere?
In attachment.
> sage
--
Regards
Luk
[-- Attachment #2: cm --]
[-- Type: application/octet-stream, Size: 3559 bytes --]
next prev parent reply other threads:[~2016-12-29 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 15:07 problem with removing osd Łukasz Chrustek
2016-12-29 19:10 ` Sage Weil
2016-12-29 20:20 ` Łukasz Chrustek
2016-12-29 20:26 ` Sage Weil
2016-12-29 20:46 ` Łukasz Chrustek
2016-12-29 20:49 ` Sage Weil
2016-12-29 20:55 ` Łukasz Chrustek [this message]
2016-12-29 21:41 ` Sage Weil
2016-12-29 22:02 ` Łukasz Chrustek
2016-12-29 22:18 ` Sage Weil
2016-12-29 23:13 ` Brad Hubbard
2016-12-29 23:33 ` Ł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=1039341611.20161229215518@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox