From: Wido den Hollander <wido@widodh.nl>
To: Sage Weil <sage@newdream.net>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: RBD stall when creating and listing images
Date: Mon, 23 Apr 2012 11:03:35 +0200 [thread overview]
Message-ID: <4F951AE7.1080707@widodh.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.1204212132530.29786@cobra.newdream.net>
On 04/22/2012 06:34 AM, Sage Weil wrote:
> On Sat, 21 Apr 2012, Wido den Hollander wrote:
>> Hi,
>>
>> I was just playing with my libvirt driver and I noticed a stall.
>>
>> On one host I had running:
>>
>> for i in {0..8192}; do rbd create --size 64 image-$i; echo "created image-$i";
>> done
>>
>> And on the other host I was running a pool-refresh in libvirt.
>>
>> As I was tailing the libvirt log I noticed that it had stalled, so I checked
>> my other terminal and saw that the creation of new images had also stalled.
>>
>> This situation persisted for about ~20 seconds and then everything started to
>> continue.
>>
>> At the moment of the stall libvirt was calling rbd_list and was not doing any
>> rbd_stat yet.
>>
>> I'm trying to reproduce it here, but I wonder if there is a logical
>> explanation for this situation?
>>
>> I'm running 0.44 on my cluster and 0.45 on the client btw.
>
> Nothing comes to mind.. unless libvirt is doing something silly on
> pool-refresh and actually modifies each image header (which would make
> users stop and refresh).
>
No, it doesn't. This is the libvirt code:
https://github.com/wido/libvirt/blob/rbd/src/storage/storage_backend_rbd.c#L312
> If you can reproduce this with some logs (ideally the stalling client),
> I'd love to see what's going on.
I think a "rbd ls" on one host and "rbd create" on another host should
give the same result.
I'll try with that and see what comes out of it.
Wido
>
> sage
prev parent reply other threads:[~2012-04-23 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:26 RBD stall when creating and listing images Wido den Hollander
2012-04-22 4:34 ` Sage Weil
2012-04-23 9:03 ` Wido den Hollander [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=4F951AE7.1080707@widodh.nl \
--to=wido@widodh.nl \
--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 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.