From: Oliver Francke <Oliver.Francke@filoo.de>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Problem after ceph-osd crash
Date: Mon, 20 Feb 2012 18:49:19 +0100 [thread overview]
Message-ID: <4F42879F.1040802@filoo.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1202200941100.30577@cobra.newdream.net>
Hi Sage,
On 02/20/2012 06:41 PM, Sage Weil wrote:
> On Mon, 20 Feb 2012, Oliver Francke wrote:
>> Hi,
>>
>> we are just in trouble after some mess with trying to include a new OSD-node
>> into our cluster.
>>
>> We get some weird "libceph: corrupt inc osdmap epoch 880 off 102
>> (ffffc9001db8990a of ffffc9001db898a4-ffffc9001db89dae)"
>>
>> on the console.
>> The whole system is in a state ala:
>>
>> 012-02-20 17:56:27.585295 pg v942504: 2046 pgs: 1348 active+clean, 43
>> active+recovering+degraded+remapped+backfill, 218 active+recovering, 437
>> active+recovering+remapped+backfill; 1950 GB data, 3734 GB used, 26059 GB /
>> 29794 GB avail; 272914/1349073 degraded (20.230%)
>>
>> and sometimes the ceph-osd on node0 is crashing. At the moment of writing, the
>> degrading continues to shrink down below 20%.
> How did ceph-osd crash? Is there a dump in the log?
'course I will provide all logs, uhm, a bit later, we are busy to start
all VM's, and handle first customer-tickets right now ;-)
To be most complete for the collection, would you be so kind to give a
list of all necessary kern.log osdX.log etc.?
Thnx for the fast reaction,
Oliver.
> sage
>
>> Any clues?
>>
>> Thnx in @vance,
>>
>> Oliver.
>>
>> --
>>
>> Oliver Francke
>>
>> filoo GmbH
>> Moltkestraße 25a
>> 33330 Gütersloh
>> HRB4355 AG Gütersloh
>>
>> Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz
>>
>> Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
--
Oliver Francke
filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh
Geschäftsführer: S.Grewing | J.Rehpöhler | C.Kunz
Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-20 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 16:59 Problem after ceph-osd crash Oliver Francke
2012-02-20 17:41 ` Sage Weil
2012-02-20 17:49 ` Oliver Francke [this message]
2012-02-20 18:05 ` 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=4F42879F.1040802@filoo.de \
--to=oliver.francke@filoo.de \
--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.