CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD crashed today in os/JournalingObjectStore.cc
Date: Thu, 06 Dec 2012 15:47:51 +0100	[thread overview]
Message-ID: <50C0B017.7020003@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1212060615100.13653@cobra.newdream.net>

Hello,

as it were crashing pretty often i had a few minutes where only 9 of 20 
OSDs were still alive i reverted back to 
3ace9a7c66c79847d215f4bd38f40ca8b07bab8e

Which works fine ;-)

Stefan

Am 06.12.2012 15:43, schrieb Sage Weil:
> On Thu, 6 Dec 2012, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> here a new dump / crash:
>> https://www.dropbox.com/s/1qhg0dd0fv17q10/ceph-osd.54.log.gz
>
> Awesome, thanks!  I see the bug now.  Working out a fix.
>
> In the meantime, you can revert 85574a36226611ccf0fb7591fd275a2bdcca2bad
> and 528108485be7912069087822e5b7a1a2f1dd515e.
>
> sage

Stefan

  reply	other threads:[~2012-12-06 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  9:56 OSD crashed today in os/JournalingObjectStore.cc Stefan Priebe - Profihost AG
2012-12-05 14:41 ` Sage Weil
2012-12-05 16:05   ` Stefan Priebe - Profihost AG
2012-12-05 22:25     ` Stefan Priebe
2012-12-05 22:29       ` Stefan Priebe
2012-12-05 23:36     ` Sage Weil
2012-12-06  9:38       ` Stefan Priebe - Profihost AG
2012-12-06 14:43         ` Sage Weil
2012-12-06 14:47           ` Stefan Priebe - Profihost AG [this message]
2012-12-07  0:38         ` Sage Weil
2012-12-07  7:49           ` Stefan Priebe - Profihost AG
2012-12-07 11:02             ` Sage Weil
2012-12-07 11:29               ` Stefan Priebe - Profihost AG

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=50C0B017.7020003@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox