From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: librbd discard bug problems -> i REALLY got it
Date: Tue, 20 Nov 2012 09:09:34 -0800 [thread overview]
Message-ID: <50ABB94E.2010003@inktank.com> (raw)
In-Reply-To: <50AB7BA3.1060906@profihost.ag>
On 11/20/2012 04:46 AM, Stefan Priebe - Profihost AG wrote:
> Hi Josh,
>
> the problem was again in the qemu rbd driver.
>
> It was using int for several return values instead of int_64. I send 2nd
> patch to the qemu list and ceph devel.
>
> Could you please care that BOTH patches the one from yesterday AND today
> get into qemu?
Great! I'll look at these later today.
> Greets,
> Stefan
> Am 20.11.2012 01:28, schrieb Josh Durgin:
>> On 11/19/2012 04:00 PM, Stefan Priebe wrote:
>>> Hi Josh,
>>>
>>> i don't get it. Every debug line i print is a prositive fine value. BUt
>>> rbd_aio_bh_cb get's called with these values. As you can see that are
>>> not much values i copied all values < 0 from log for discarding a whole
>>> 30GB device.
>>
>> Could you post the patch of the debug prints you added and the log?
prev parent reply other threads:[~2012-11-20 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 21:19 librbd discard bug problems -> i got it Stefan Priebe
2012-11-19 22:38 ` Josh Durgin
2012-11-19 22:45 ` Stefan Priebe
2012-11-19 22:48 ` Josh Durgin
2012-11-19 23:16 ` Stefan Priebe
2012-11-19 23:33 ` Josh Durgin
2012-11-19 23:42 ` Stefan Priebe
2012-11-19 23:47 ` Josh Durgin
2012-11-20 0:00 ` Stefan Priebe
2012-11-20 0:28 ` Josh Durgin
2012-11-20 9:50 ` Stefan Priebe - Profihost AG
2012-11-20 12:46 ` librbd discard bug problems -> i REALLY " Stefan Priebe - Profihost AG
2012-11-20 17:09 ` Josh Durgin [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=50ABB94E.2010003@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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