All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: how to free space from rados bench comman?
Date: Thu, 24 May 2012 10:22:08 +0200	[thread overview]
Message-ID: <4FBDEFB0.3030700@widodh.nl> (raw)
In-Reply-To: <4FBDE57F.9010409@profihost.ag>



On 24-05-12 09:38, Stefan Priebe - Profihost AG wrote:
> Am 24.05.2012 09:28, schrieb Wido den Hollander:
>> Hi,
>>
>> On 24-05-12 09:01, Stefan Priebe - Profihost AG wrote:
>>> Hi,
>>>
>>> every rados bench write uses disk space and my space fills up. How to
>>> free this space again?
>>>
>>> Used command?
>>> rados -p data bench 60 write -t 16
>>
>> What does this show:
>>
>> $ rados -p data ls|wc -l
>
> ~# rados -p data ls|wc -l
> 46631

That is weird, I thought the bench tool cleaned up it's "mess".

Imho it should cleanup after it's done, but there might be a reason why 
it's not. Did you abort the benchmark or did you let it do the whole run?

>
> I do not use the data pool so it is seperate ;-) i only use the rbd pool
> for block devices.
>
> So i will free the space with:
> for i in `rados -p data ls`; do echo $i; rados -p data rm $i; done

rados -p data ls|xargs -n 1 rados -p data rm

I love shorter commands ;)

Wido

>
> Thanks!
>
> Stefan
> --
> 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

  reply	other threads:[~2012-05-24  8:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  7:01 how to free space from rados bench comman? Stefan Priebe - Profihost AG
2012-05-24  7:28 ` Wido den Hollander
2012-05-24  7:38   ` Stefan Priebe - Profihost AG
2012-05-24  8:22     ` Wido den Hollander [this message]
2012-05-24  8:51       ` Stefan Priebe - Profihost AG
2012-05-24 17:55         ` Greg Farnum
2012-05-24 18:05           ` Josh Durgin
2012-05-24 18:14             ` Greg Farnum

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=4FBDEFB0.3030700@widodh.nl \
    --to=wido@widodh.nl \
    --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 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.