From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Gregory Farnum <greg@inktank.com>
Cc: Wido den Hollander <wido@widodh.nl>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: KVM/RBD Block device hangs
Date: Tue, 22 May 2012 14:47:09 +0200 [thread overview]
Message-ID: <4FBB8ACD.8040401@profihost.ag> (raw)
In-Reply-To: <CAPYLRzgpKPU0cu85nUrH96B8=EfM=QPD=jjfWPHRz1N9MdCRVw@mail.gmail.com>
Am 21.05.2012 22:57, schrieb Gregory Farnum:
> On Mon, May 21, 2012 at 1:51 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> Am 21.05.2012 16:59, schrieb Wido den Hollander:
>>
>>> Probably after, but both is fine. I just want to know how your cluster
>>> is doing and what the PG states are.
>>
>> will do so.
>>
>> dmesg says at least:
>> [ 4975.850765] ceph-osd[6226]: segfault at 439d34000 ip 00007f0db39bfb23 sp
>> 00007f0da8c5e240 error 4 in libtcmalloc.so.0.0.0[7f0db399b000+3d000]
>
> This is not an error we've seen before, and it's a little scary. Can you
> 1) run gdb and get a backtrace and a printout of each frame in the trace?
> 2) reproduce with high-level OSD debug logging enabled?
I haven't seen this problem again with v0.47 i will report back if i see
it again.
Stefan
prev parent reply other threads:[~2012-05-22 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 14:44 KVM/RBD Block device hangs Stefan Priebe - Profihost AG
2012-05-21 14:47 ` Wido den Hollander
2012-05-21 14:50 ` Stefan Priebe - Profihost AG
2012-05-21 14:59 ` Wido den Hollander
2012-05-21 20:51 ` Stefan Priebe
2012-05-21 20:57 ` Gregory Farnum
2012-05-22 12:47 ` Stefan Priebe - Profihost AG [this message]
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=4FBB8ACD.8040401@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=wido@widodh.nl \
/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.