All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Chris Dunlop <chris@onthe.net.au>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Speed up 'rbd rm'
Date: Thu, 30 May 2013 13:50:14 -0700	[thread overview]
Message-ID: <51A7BB86.3020106@inktank.com> (raw)
In-Reply-To: <20130530022307.GA27809@onthe.net.au>

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.
>
> Thanks. I'll see how I go, I may just leave the 'rm' running all
> weekend rather than futzing around recompiling ceph and getting
> off the mainline track.

If you're mainly interested in getting rid of the accidentally 1.5PB
image, you can just delete the header (and id object if it's format 2)
and then 'rbd rm' will just remove it from the rbd_directory index, and
not try to delete all the non-existent data objects.

> Perhaps as a low-churn high-impact (for those that need it) change,
> this is a candidate to be back-patched into 0.61.3 and perhaps 0.56.7 ?
>
> Cheers,
>
> Chris.


  reply	other threads:[~2013-05-30 20:50 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 [this message]
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

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=51A7BB86.3020106@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chris@onthe.net.au \
    /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.