I'm not really concerned about the reporting aspect, I can look in the storage 
vendor UI to see that. My concern is: will oVirt stop provisioning storage in 
the domain because it *thinks* the domain is full. De-dup is currently running 
at about 2.5:1 so I'm concerned that oVirt will think the domain is full way 
before it actually is.



Not clear if this is handled natively in oVirt or by the underlying lvs?


---- On Fri, 21 Feb 2020 21:35:06 +0000 Nir Soffer <[email protected]> wrote 
----




On Fri, Feb 21, 2020, 17:14 Alan G <mailto:alan%[email protected]> 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


_______________________________________________
Users mailing list -- mailto:[email protected]
To unsubscribe send an email to mailto:[email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/BKCQYELRW5XP5BVDPSJJ76YZD3N37LVF/
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/Z627L5LITUZV3XWRHVS775GIJSZ7KVV2/

Reply via email to