On Fri, Jan 11, 2019 at 3:23 PM Leo David <leoalex@gmail.com> wrote:
Hello Everyone, I'm I trying to benefit of vdo capabilities, but it seems that I don;t have too much luck with this. I have both created a vdo based gluster volume usign both following methods: - at hyperconverged wizard cluster setup by enabling compression per device - after installation, by creating a new gluster volume and enabling compression
In both cases, I end up with a real device size gluster volume/storage domain, although the vdo's appear in node's cockpit UI as being 10 times then physical device.
ie: 3 nodes, each having 1 x 900GB ssd device, turns into 9t device vdo device per host, but the storage domain (gluster replica 3 ) ends up as being 900GB . Am I missing something , or maybe doing something wrong? Thank you very much !
You're running into this bug - https://bugzilla.redhat.com/show_bug.cgi?id=1629543 As a workaround, can you try lvextend on the gluster bricks to make use of the available capacity?
Leo
Best regards, Leo David _______________________________________________ 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/F5CWQ2AYXCVUG2...