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: Thu, 15 Sep 2011 23:10:41 +0200	[thread overview]
Message-ID: <4E7269D1.6010804@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1109151302160.17623@cobra.newdream.net>

Hi Sage,
that's quite a bit of output, I put it in a pastebin. 
http://pastebin.com/9CNJk0Pw.

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'
> 

  reply	other threads:[~2011-09-15 21:10 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 [this message]
2011-09-15 22:54           ` Sage Weil
2011-09-16  9:05             ` Martin Mailand
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=4E7269D1.6010804@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