https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infr...
The logical volumes that comprise the engine gluster volume must be
thick provisioned. This protects the Hosted Engine from out of space conditions,
disruptive volume configuration changes, I/O overhead, and migration activity.
Or is that extremely dated information?
Am 18. September 2022 21:08:45 MESZ schrieb Strahil Nikolov via Users
<users(a)ovirt.org>:
>Can you share the RH recommendation to use Thick LV ?
>Best Regards,Strahil NikolovĀ
>
> I don't have that anymore, but I assume that gluster_infra_lv_logicalvols
requires a thin pool:
https://github.com/gluster/gluster-ansible-infra/blob/master/roles/backen...
>_______________________________________________
>Users mailing list -- users(a)ovirt.org
>To unsubscribe send an email to users-leave(a)ovirt.org
>Privacy Statement:
https://www.ovirt.org/privacy-policy.html
>oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XQ4Q4SELENO...
>