From: Alex Elder <elder@inktank.com>
To: Nick Bartos <nick@pistoncloud.com>
Cc: Sage Weil <sage@inktank.com>, Gregory Farnum <greg@inktank.com>,
Josh Durgin <josh.durgin@inktank.com>,
Mandell Degerness <mandell@pistoncloud.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: rbd map command hangs for 15 minutes during system start up
Date: Fri, 14 Dec 2012 10:46:26 -0600 [thread overview]
Message-ID: <50CB57E2.10703@inktank.com> (raw)
In-Reply-To: <CAPud5_6q0gQD0ajpKZdvnaaMBvapQ59fkOA7ANVhPo0dMGJ+Sw@mail.gmail.com>
On 12/13/2012 01:00 PM, Nick Bartos wrote:
> Here's another log with the kernel debugging enabled:
> https://gist.github.com/raw/4278697/1c9e41d275e614783fbbdee8ca5842680f46c249/rbd-hang-1355424455.log
>
> Note that it hung on the 2nd try.
Just to make sure I'm working with the right code base, can
you confirm that you're using a kernel built with the equivalent
of what's now in the "wip-nick-newer" branch (commit id 1728893)?
Also, looking at this log I don't think I see any rbd debug output.
Does that make sense to you?
How are you activating debugging to get these messages?
If it includes something like:
echo module libceph +p > /sys/kernel/debug/dynamic_debug/control
it might be that you need to also do:
echo module rbd +p > /sys/kernel/debug/dynamic_debug/control
This information would be helpful in providing some more context
about what rbd is doing that's leading to the various messaging
activity I seen in this log.
Please send me a log with that info if you are able to produce
one. Thanks a lot.
-Alex
next prev parent reply other threads:[~2012-12-14 16:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 22:10 rbd map command hangs for 15 minutes during system start up Mandell Degerness
2012-11-09 1:43 ` Josh Durgin
2012-11-12 22:19 ` Nick Bartos
2012-11-12 23:16 ` Sage Weil
2012-11-16 0:21 ` Nick Bartos
2012-11-16 0:25 ` Sage Weil
2012-11-16 18:36 ` Nick Bartos
2012-11-16 19:16 ` Sage Weil
2012-11-16 22:01 ` Nick Bartos
2012-11-16 22:13 ` Sage Weil
2012-11-16 22:16 ` Nick Bartos
2012-11-16 22:21 ` Sage Weil
2012-11-19 23:04 ` Nick Bartos
2012-11-19 23:34 ` Gregory Farnum
2012-11-20 21:53 ` Nick Bartos
2012-11-21 1:31 ` Nick Bartos
2012-11-21 16:50 ` Sage Weil
2012-11-21 17:02 ` Nick Bartos
2012-11-21 17:34 ` Nick Bartos
2012-11-21 21:41 ` Nick Bartos
2012-11-22 4:47 ` Sage Weil
2012-11-22 5:49 ` Nick Bartos
2012-11-22 18:04 ` Nick Bartos
2012-11-29 20:37 ` Alex Elder
2012-11-30 18:49 ` Nick Bartos
2012-11-30 19:10 ` Alex Elder
2012-11-30 19:31 ` Sage Weil
2012-11-30 23:22 ` Alex Elder
2012-12-02 5:34 ` Nick Bartos
2012-12-03 4:43 ` Alex Elder
2012-12-10 21:57 ` Alex Elder
2012-12-11 17:26 ` Nick Bartos
2012-12-11 18:01 ` Alex Elder
2012-12-11 19:44 ` Alex Elder
2012-12-13 0:57 ` Nick Bartos
2012-12-13 19:00 ` Nick Bartos
2012-12-13 19:07 ` Alex Elder
2012-12-14 16:46 ` Alex Elder [this message]
2012-12-14 16:53 ` Nick Bartos
2012-12-14 18:03 ` Alex Elder
2012-12-17 17:12 ` Nick Bartos
2012-12-18 16:09 ` Alex Elder
2012-12-18 18:05 ` Nick Bartos
2012-12-19 21:25 ` Alex Elder
2012-12-19 22:42 ` Alex Elder
2012-12-20 17:48 ` Nick Bartos
2012-12-20 21:59 ` Alex Elder
2012-12-26 17:45 ` Nick Bartos
2012-12-26 17:50 ` Alex Elder
2012-12-26 21:36 ` Alex Elder
2012-12-27 17:33 ` Nick Bartos
2012-12-27 18:43 ` Sage Weil
2012-12-27 19:41 ` Alex Elder
2012-12-31 18:22 ` Alex Elder
2013-01-02 15:56 ` Nick Bartos
2012-11-16 22:23 ` Gregory Farnum
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=50CB57E2.10703@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=josh.durgin@inktank.com \
--cc=mandell@pistoncloud.com \
--cc=nick@pistoncloud.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox