Thank you everyone, I didn't really realize that my friends made so many thin
disks.
The storage.alloction.overprovisioning.factor parameter could be useful, what
is the point of using thin disks if the capacity of the pool cannot be exceeded?
MariaDB [cloud]> select round(size/1024/1024/1024,
Wow.. . That's the community spirit - 3 replies in 8min from the original
email!
On Tue, Sep 17, 2019, 08:07 Andrija Panic wrote:
> Hi Piotr,
>
> Allocated should be the sum of all disks virtual size from the DB,
> "volumes" table.
>
> Can you do select sum "size" from that table, where pool_id=
Hi Piotr,
Allocated should be the sum of all disks virtual size from the DB,
"volumes" table.
Can you do select sum "size" from that table, where pool_id=xxx and removed
is NULL (on my mobile, can't remember the name of the column in the table,
probability just "size").
More importantly, I'm won
Disk allocated != Disk used. It's for how much all volumes will span when
their thin provisioning optimization stops and they fully use the space.
вт, 17 сент. 2019 г., 13:00 Piotr Pisz :
> Hi all,
>
> I have a strange situation, we have a CephFS share mounted as
> SharedMountPoint.
> CS shows Di
Hello Piotr,
Are you using thin provisioning for disk offerings?
With regards
Thomas
On Tue, 17 Sep 2019, 7:00 am Piotr Pisz, wrote:
> Hi all,
>
> I have a strange situation, we have a CephFS share mounted as
> SharedMountPoint.
> CS shows Disk Total as 12T (that's ok), while Disk Allocated sh
Hi all,
I have a strange situation, we have a CephFS share mounted as SharedMountPoint.
CS shows Disk Total as 12T (that's ok), while Disk Allocated shows like 11.8T
(it's not ok, disk is 50% full).
How can We diagnose the cause?
Regards,
Piotr
