From: Alex Elder <elder@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Nick Bartos <nick@pistoncloud.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: Thu, 27 Dec 2012 13:41:49 -0600 [thread overview]
Message-ID: <50DCA47D.2030300@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212271042500.22449@cobra.newdream.net>
On 12/27/2012 12:43 PM, Sage Weil wrote:
> On Thu, 27 Dec 2012, Nick Bartos wrote:
>> I have some exciting news. After 215 test runs, no hung processes
>> were detected. I think we may actually have it this time. Thanks for
>> all your hard work!
This is great news Nick, and I really appreciate your help testing so
we could get rid of this ugly thing.
> Sweet! I think it was the new branch naming scheme that did it.
Obviously.
I'm going to blow away all the wip-nick-new* branches.
-Alex
>
> sage
>
>>
>> -Nick
>>
>> On Wed, Dec 26, 2012 at 1:36 PM, Alex Elder <elder@inktank.com> wrote:
>>> On 12/26/2012 11:45 AM, Nick Bartos wrote:
>>>> Here's a log with a hang on the updated branch:
>>>>
>>>> https://gist.github.com/raw/4381750/772476e1bae1e6366347a223f34aa6c440b92765/rdb-hang-1356543132.log
>>>
>>> OK, new naming scheme. Please try: wip-nick-1
>>>
>>> I added another simple fix, but then collapsed three commits
>>> into one, and added one more (somewhat unrelated).
>>>
>>> I've done simple testing with this and will subject it to
>>> more rigorous testing shortly. I wanted to make it available
>>> to you quickly though.
>>>
>>> -Alex
>>
>>
next prev parent reply other threads:[~2012-12-27 19:41 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
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 [this message]
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=50DCA47D.2030300@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