Gluster snapshots on hyperconverged with VDO ?

I evaluate deploying ovirt 4.2 on centos 7.5 with VDO dedup in production. When deploying gluster with cockpit, after selecting deduplication/compression, the option to have the brick thin provisioned is grayed out. As a result, gluster snapshots are not possible. : - Neither in CLI : "snapshot create: failed: Snapshot is supported only for thin provisioned LV. Ensure that all bricks of data are thinly provisioned LV. " - Nor through the scheduler in volume management : I see the icon "Volume snapshots are scheduled" but I do not see any being created. There are no snapshot creation failure message in the manager. So I have two questions : - At deployment, is changing the gdeploy option manually from thick to thin supported for a LV on VDO device(or even a good idea)? - Should I open a bug report?

Hi, Anyone with experience with vdo on Hyperconverged with ovirt 4.2.7? Should I force thin provisioning for lv in gdeploy's conf in order to have working gluster snapshots? I am not sure about the status of dedup in ovirt 4.2/hyperconverged. Supported, advised or not?

On Wed, Oct 17, 2018 at 6:42 PM <guillaume.pavese@interact-iv.com> wrote:
Hi,
Anyone with experience with vdo on Hyperconverged with ovirt 4.2.7? Should I force thin provisioning for lv in gdeploy's conf in order to have working gluster snapshots?
I am not sure about the status of dedup in ovirt 4.2/hyperconverged. Supported, advised or not?
Thin provisioning was disabled with vdo due to a bug with discards not working. _______________________________________________
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org 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/users@ovirt.org/message/36AHJEVWOSAVL7...

Thank you for this information. I guess I should at least wait for that bug to be resolved before deploying in production. Do you have the bugzilla reference so I could track it?

On Wed, Oct 17, 2018 at 7:15 PM <guillaume.pavese@interact-iv.com> wrote:
Thank you for this information. I guess I should at least wait for that bug to be resolved before deploying in production. Do you have the bugzilla reference so I could track it?
https://bugzilla.redhat.com/show_bug.cgi?id=1600156 _______________________________________________
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org 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/users@ovirt.org/message/EGXDS6Y2VPKWY5...
participants (2)
-
guillaume.pavese@interact-iv.com
-
Sahina Bose