From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: still crashing osds with next branch
Date: Wed, 20 Jun 2012 22:21:55 +0200 [thread overview]
Message-ID: <4FE230E3.1040400@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206201110540.14284@cobra.newdream.net>
Am 20.06.2012 20:11, schrieb Sage Weil:
> On Wed, 20 Jun 2012, Stefan Priebe wrote:
>> Am 20.06.2012 19:35, schrieb Sage Weil:
>>> On Wed, 20 Jun 2012, Stefan Priebe wrote:
>>>> Nobody an idea? Should i open up bugs in tracker?
>>>
>>> Let's open up bugs. If they are reproducible, debug osd = 20 logs would
>>> be awesome!
>>>
>>> Also, the crash you mentioned in your earlier email we did see:
>>>
>>> http://tracker.newdream.net/issues/2599
>>>
>>> If you have logs from that crash, those would also be helpful.
>>
>> i can't reproduce but it happens pretty often. So i can switch to debug osd =
>> 20 in general. What else do you need?
>
> That will probably be enough, but if you get a core file, don't throw it
> away :)
Hi first log is 2.6GB and core dump 643MB? Where to put this?
Stefan
next prev parent reply other threads:[~2012-06-20 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 10:03 still crashing osds with next branch Stefan Priebe - Profihost AG
2012-06-20 13:30 ` Stefan Priebe - Profihost AG
2012-06-20 17:19 ` Stefan Priebe
2012-06-20 17:35 ` Sage Weil
2012-06-20 18:10 ` Stefan Priebe
2012-06-20 18:11 ` Sage Weil
2012-06-20 20:21 ` Stefan Priebe [this message]
2012-06-20 22:56 ` Sage Weil
2012-06-21 5:54 ` 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=4FE230E3.1040400@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 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.