From: Dan Mick <dan.mick@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Sam Just <sam.just@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: reproducable osd crash
Date: Mon, 25 Jun 2012 14:01:51 -0700 [thread overview]
Message-ID: <4FE8D1BF.3090108@inktank.com> (raw)
In-Reply-To: <4FE89DB0.1080606@profihost.ag>
On 06/25/2012 10:19 AM, Stefan Priebe wrote:
>
>> I've yet to make the core match the binary.
>
> I'm sorry. Is there a way to provide more / better information.
>
> Stefan
Well, I was still looking at the possibility that it was my problem, but
here are versions:
- the osd binary you sent is version 0.47.2-521-g88c7629, corresponding
to sha1 5ce8d71fb6d2e3065c8b274e196c26288c7a93d0
- the corefile is from version 0.47.3 (sha1
c467d9d1b2eac9d3d4706b8e044979aa63b009f8)
Using any combination of your binary or my build of the binary from
either version does not result in a matching stack backtrace from gdb.
If you can get a corefile and binary that match and send them again,
perhaps we can get further; I'm not sure why what you sent didn't seem
to match. Are you running the same version of Ceph on each host?
next prev parent reply other threads:[~2012-06-25 21:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:55 reproducable osd crash Stefan Priebe - Profihost AG
2012-06-21 13:07 ` Stefan Priebe - Profihost AG
2012-06-21 13:13 ` Stefan Priebe - Profihost AG
2012-06-21 13:23 ` Stefan Priebe - Profihost AG
2012-06-21 19:57 ` Stefan Priebe
2012-06-22 16:01 ` Stefan Priebe - Profihost AG
2012-06-22 6:43 ` Stefan Priebe
2012-06-22 22:56 ` Dan Mick
2012-06-22 23:59 ` Sam Just
2012-06-23 6:32 ` Stefan Priebe
2012-06-25 16:39 ` Dan Mick
2012-06-25 17:19 ` Stefan Priebe
2012-06-25 21:01 ` Dan Mick [this message]
2012-06-25 21:18 ` Stefan Priebe
2012-06-26 0:11 ` Dan Mick
2012-06-26 5:15 ` Stefan Priebe
2012-06-26 5:48 ` Stefan Priebe
2012-06-26 16:05 ` Tommi Virtanen
2012-06-26 16:47 ` Stefan Priebe
2012-06-26 18:01 ` Sam Just
2012-06-27 7:22 ` Stefan Priebe - Profihost AG
2012-06-27 15:19 ` Sage Weil
2012-06-23 0:26 ` Dan Mick
2012-06-23 6:32 ` Stefan Priebe
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=4FE8D1BF.3090108@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=sam.just@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.