CEPH filesystem development
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph kernel bug
Date: Fri, 16 Sep 2011 11:05:11 +0200	[thread overview]
Message-ID: <4E731147.6010405@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1109151551250.27715@cobra.newdream.net>

Hi Sage,
I rerun the test and I think I triggered the first bug again.
http://pastebin.com/ydNm0pff

I did also the dumps for you.
http://tuxadero.com/multistorage/ceph.ko_dump
http://tuxadero.com/multistorage/libceph.ko_dump

Best Regards,
  martin
Am 16.09.2011 00:54, schrieb Sage Weil:
> On Thu, 15 Sep 2011, Martin Mailand wrote:
>> Hi Sage,
>> that's quite a bit of output, I put it in a pastebin.
>> http://pastebin.com/9CNJk0Pw.
> Any chance you can include the output of 'objdump -rdS libceph.ko'?
> ceph.ko too, for good measure.
>
> This looks like a sightly different crash than the one on that bug!
>
> Thanks!
> sage
>
>
>> Best Regards,
>>   martin
>>
>> Sage Weil schrieb:
>>> On Thu, 15 Sep 2011, Martin Mailand wrote:
>>>> Hi Sage,
>>>> I am still hitting this in -rc6. It happeneds every time I stop an OSD.
>>>> Do you need more information to reproduce it?
>>> Oh, great to hear it's easy to reproduce!  I was trying (in my uml
>>> environment) and failing.
>>>
>>> Can run the script below right before stopping the osd, and send the dmesg
>>> output along?  (Or attach to http://tracker.newdream.net/issues/1382)
>>>
>>> Thanks!
>>> sage
>>>
>>>
>>> #!/bin/sh -x
>>>
>>> p() {
>>>   echo "$*">  /sys/kernel/debug/dynamic_debug/control
>>> }
>>>
>>> p 'module ceph +p'
>>> p 'module libceph +p'
>>> p 'module rbd +p'
>>> p 'file net/ceph/messenger.c -p'
>>> p 'file' `grep -- --- /sys/kernel/debug/dynamic_debug/control | grep ceph \
>>> 	| awk '{print $1}' | sed 's/:/ line /'` '+p'
>>> p 'file' `grep -- === /sys/kernel/debug/dynamic_debug/control | grep ceph \
>>> 	| awk '{print $1}' | sed 's/:/ line /'` '+p'
>>>
>> --
>> 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
>>
>>
> --
> 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


  reply	other threads:[~2011-09-16  9:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10 21:12 ceph kernel bug Martin Mailand
2011-09-10 22:47 ` Sage Weil
2011-09-10 23:46   ` Martin Mailand
2011-09-15 19:41     ` Martin Mailand
2011-09-15 20:06       ` Sage Weil
2011-09-15 21:10         ` Martin Mailand
2011-09-15 22:54           ` Sage Weil
2011-09-16  9:05             ` Martin Mailand [this message]
2011-09-16 18:22               ` Sage Weil
2011-09-16 20:17                 ` Martin Mailand

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=4E731147.6010405@tuxadero.com \
    --to=martin@tuxadero.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox