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 14:47:26 +0200	[thread overview]
Message-ID: <4FDF235E.8030301@widodh.nl> (raw)
In-Reply-To: <4FDF1A31.6010606@profihost.ag>

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

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.

There is also no such thing as "free pool space", you have to look at 
the free cluster space.

But again, if you cluster has X TB of free space and you have multiple 
pools, your usage will depend on the amount of written data and the 
replication level.

If you want to know the usage of the rbd pool I suggest using "rados df".

The RBD tool could however be modified to show the image size if you 
give another flag.

$ rbd --extended ls

Wido

On 06/18/2012 02:08 PM, Stefan Priebe - Profihost AG wrote:
> 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 12:47 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 [this message]
2012-06-18 13:03   ` Stefan Priebe - Profihost AG
2012-06-18 13:10     ` Wido den Hollander
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=4FDF235E.8030301@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.