This usually means there are snapshotted objects still sticking around.
It's turned out to be quite the usability bugbear, but we don't have a
solution yet...
-Greg
On Wed, Nov 15, 2017 at 7:23 AM Karun Josy wrote:
> Help?!
>
> There seems to be many objects still present in the pool :
> ---
If you know that the pool should be empty, there wouldn't be a problem with
piping the ouput of `rados ls` to `rados rm`. By the same notion, if
nothing in the pool is needed you can delete the pool and create a new one
that will be perfectly empty.
On Tue, Nov 14, 2017 at 3:23 PM Karun Josy wro
Help?!
There seems to be many objects still present in the pool :
-
$ rados df
POOL_NAME USED OBJECTS CLONES COPIES MISSING_ON_PRIMARY UNFOUND
DEGRADED RD_OPSRDWR_OPSWR
vm 886 105 0 315 0
0094339
Hello Karun,
On Tue, Nov 14, 2017 at 04:16:51AM +0530, Karun Josy wrote:
> Hello,
>
> Recently, I deleted all the disks from an erasure pool 'ecpool'.
> The pool is empty. However the space usage shows around 400GB.
> What might be wrong?
>
>
> $ rbd ls -l ecpool
> $ $ ceph df
>
> GLOBAL:
> SIZ
Hello,
Recently, I deleted all the disks from an erasure pool 'ecpool'.
The pool is empty. However the space usage shows around 400GB.
What might be wrong?
$ rbd ls -l ecpool
$ $ ceph df
GLOBAL:
SIZE AVAIL RAW USED %RAW USED
19019G 16796G2223G 11.69
PO
