[ovirt-users] Re: oVirt behavior with thin provision/deduplicated block storage
On Fri, Feb 21, 2020, 17:14 Alan G <alan+ovirt(a)griff.me.uk> wrote:
Hi,
I have an oVirt cluster with a storage domain hosted on a FC storage array
that utilises block de-duplication technology. oVirt reports the capacity
of the domain as though the de-duplication factor was 1:1, which of course
is not the case. So what I would like to understand is the likely behavior
of oVirt when the used space approaches the reported capacity. Particularly
around the critical action space blocker.
oVirt does not know about the underlying block storage thin provisioning
implemention so it cannot help with this.
You will have to use the underlying storage separately to learn about the
actual allocation.
This is unlikely to change for legacy storage, but for Managed Block
Storage (conderlib) we may have a way to access such info.
Gorka, do we have any support in cinderlib for getting info about storage
alllocation and deduplication?
Nir
Attachments:
- attachment.html (text/html — 1.6 KB)