From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josh Durgin <jdurgin@redhat.com>, Jason Dillaman <dillaman@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: upstream/firefly exporting the same snap 2 times results in different exports
Date: Wed, 22 Jul 2015 09:03:55 +0200 [thread overview]
Message-ID: <55AF405B.4050602@profihost.ag> (raw)
In-Reply-To: <55AEB0B1.6040500@redhat.com>
Am 21.07.2015 um 22:50 schrieb Josh Durgin:
> Yes, I'm afraid it sounds like it is. You can double check whether the
> watch exists on an image by getting the id of the image from 'rbd info
> $pool/$image | grep block_name_prefix':
>
> block_name_prefix: rbd_data.105674b0dc51
>
> The id is the hex number there. Append that to 'rbd_header.' and you
> have the header object name. Check whether it has watchers with:
>
> rados listwatchers -p $pool rbd_header.105674b0dc51
>
> If that doesn't show any watchers while the image is in use by a vm,
> it's #9806.
Yes it does not show any watchers.
> I just merged the backport for firefly, so it'll be in 0.80.11.
> Sorry it took so long to get to firefly :(. We'll need to be
> more vigilant about checking non-trivial backports when we're
> going through all the bugs periodically.
That would be really important. I've seen that this one was already in
upstream/firefly-backports. What's the purpose of that branch?
Greets,
Stefan
> Josh
>
> On 07/21/2015 12:52 PM, Stefan Priebe wrote:
>> So this is really this old bug?
>>
>> http://tracker.ceph.com/issues/9806
>>
>> Stefan
>> Am 21.07.2015 um 21:46 schrieb Josh Durgin:
>>> On 07/21/2015 12:22 PM, Stefan Priebe wrote:
>>>>
>>>> Am 21.07.2015 um 19:19 schrieb Jason Dillaman:
>>>>> Does this still occur if you export the images to the console (i.e.
>>>>> "rbd export cephstor/disk-116@snap - > dump_file")?
>>>>>
>>>>> Would it be possible for you to provide logs from the two "rbd export"
>>>>> runs on your smallest VM image? If so, please add the following to
>>>>> the "[client]" section of your ceph.conf:
>>>>>
>>>>> log file = /valid/path/to/logs/$name.$pid.log
>>>>> debug rbd = 20
>>>>>
>>>>> I opened a ticket [1] where you can attach the logs (if they aren't
>>>>> too large).
>>>>>
>>>>> [1] http://tracker.ceph.com/issues/12422
>>>>
>>>> Will post some more details to the tracker in a few hours. It seems it
>>>> is related to using discard inside guest but not on the FS the osd is
>>>> on.
>>>
>>> That sounds very odd. Could you verify via 'rados listwatchers' on an
>>> in-use rbd image's header object that there's still a watch established?
>>>
>>> Have you increased pgs in all those clusters recently?
>>>
>>> Josh
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-22 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 12:29 upstream/firefly exporting the same snap 2 times results in different exports Stefan Priebe - Profihost AG
2015-07-21 14:32 ` Jason Dillaman
2015-07-21 16:55 ` Stefan Priebe
2015-07-21 17:19 ` Jason Dillaman
2015-07-21 19:22 ` Stefan Priebe
2015-07-21 19:46 ` Josh Durgin
2015-07-21 19:48 ` Stefan Priebe
2015-07-21 20:48 ` Jason Dillaman
2015-07-21 19:52 ` Stefan Priebe
2015-07-21 20:50 ` Josh Durgin
2015-07-22 7:03 ` Stefan Priebe - Profihost AG [this message]
2015-07-22 10:27 ` Nathan Cutler
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=55AF405B.4050602@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=jdurgin@redhat.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 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.