From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Chris Dunlop <chris@onthe.net.au>, ceph-devel@vger.kernel.org
Subject: Re: Speed up 'rbd rm'
Date: Fri, 31 May 2013 16:53:45 -0700 [thread overview]
Message-ID: <51A93809.6090802@inktank.com> (raw)
In-Reply-To: <51A845F2.8050001@profihost.ag>
On 05/30/2013 11:40 PM, Stefan Priebe - Profihost AG wrote:
> Am 31.05.2013 03:40, schrieb Chris Dunlop:
>> On Thu, May 30, 2013 at 01:50:14PM -0700, Josh Durgin wrote:
>>> On 05/29/2013 07:23 PM, Chris Dunlop wrote:
>>>> On Wed, May 29, 2013 at 12:21:07PM -0700, Josh Durgin wrote:
>>>>> On 05/28/2013 10:59 PM, Chris Dunlop wrote:
>>>>>> I see there's a new commit to speed up an 'rbd rm':
>>>>>>
>>>>>> http://tracker.ceph.com/projects/ceph/repository/revisions/40956410169709c32a282d9b872cb5f618a48926
>>>>>>
>>>>>> Is it safe to cherry-pick this commit on top of 0.56.6 (or, if not, v0.61.2) to speed up the remove?
>>>>>
>>>>> You'll need 537386d906b8c0e395433461dcb03a82eb33f34f as well. It should
>>>>> apply cleanly to 0.61.2, and probably 0.56.6 too.
>
> I cherry picked both on top of cuttlefish it works but not very good.
> rbd command finishes but rbd image is still in rbd ls and just gets
> deleted later. I also saw a variant, where rbd rm outputs errors even
> though the image was there but it still got deleted...
I forgot that there was a bug in the original version. You'll need
395a775a8c87b0ee1ce314257e25240214f4081c too.
prev parent reply other threads:[~2013-05-31 23:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 5:59 Speed up 'rbd rm' Chris Dunlop
2013-05-29 19:21 ` Josh Durgin
2013-05-30 2:23 ` Chris Dunlop
2013-05-30 20:50 ` Josh Durgin
2013-05-30 21:09 ` Smart Weblications GmbH - Florian Wiessner
2013-05-31 1:40 ` Chris Dunlop
2013-05-31 2:04 ` Josh Durgin
2013-06-03 9:15 ` Chris Dunlop
2013-05-31 6:40 ` Stefan Priebe - Profihost AG
2013-05-31 23:53 ` 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=51A93809.6090802@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chris@onthe.net.au \
--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