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: extent rbd ls to show size and free space?
Date: Mon, 18 Jun 2012 15:10:23 +0200	[thread overview]
Message-ID: <4FDF28BF.1090600@widodh.nl> (raw)
In-Reply-To: <4FDF270C.7010606@profihost.ag>

On 06/18/2012 03:03 PM, Stefan Priebe - Profihost AG wrote:
> Am 18.06.2012 14:47, schrieb Wido den Hollander:
>> Hi,
>>
>> > Hello list,
>> >
>> > are there any plans to extent rbd ls in a way that it shows, image size
>> > and free space of the pool?
>> >
>>
>> You want something like:
>>
>> $ rbd ls
>> NAME SIZE
>> alpha 50G
>> beta 400G
>> charlie 150G
>
> Yes
>
>> That is possible, but if you want to see the allocation of an image that
>> will be harder, since RBD doesn't know which objects have been written
>> to and which haven't.
>
> Sure i didn't mean that.
>
>> If you want to know the usage of the rbd pool I suggest using "rados df".
> ah OK.
>
>> The RBD tool could however be modified to show the image size if you
>> give another flag.
>>
>> $ rbd --extended ls
> That would be great.

I created an issue in the tracker for it: 
http://tracker.newdream.net/issues/2601

>
> 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-06-18 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 12:08 extent rbd ls to show size and free space? Stefan Priebe - Profihost AG
2012-06-18 12:47 ` Wido den Hollander
2012-06-18 13:03   ` Stefan Priebe - Profihost AG
2012-06-18 13:10     ` Wido den Hollander [this message]
2012-06-18 13:11       ` Stefan Priebe - Profihost AG

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=4FDF28BF.1090600@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.