On Wed, Aug 1, 2018 at 3:12 PM, Jayme <jay...@gmail.com> wrote: > I burned the node image yesterday 4.2.5.1 July 31. I've been playing with > Ovirt install for the past week and burned node iso a few times and this > image is the first time I've ever seen vdo options in gdeploy. > > How do I make sure I have the most recent version of gdeploy, is node > behind? > > Also can anyone chime in about vdo, is it recommended for use now? What > is its main benefit, does it offer performance boost or more for saving > disk space? >
VDO provides dedupe/compression at the block layer. More at https://github.com/dm-vdo/kvdo It provides space savings, but there's a performance drop depending on the workloads you run. It's better to turn on VDO if you're using SSD devices as the performance decrease is less noticeable. But please run your own benchmark tests to decide. The vdo kernel module has been available since CentOS 7.5 > On Wed, Aug 1, 2018, 2:04 AM Gobinda Das, <go...@redhat.com> wrote: > >> Hi, >> Looks like you are using older version of gdeploy. Can you please >> specify the gdeploy version? >> >> On Wed, 1 Aug 2018, 12:55 a.m. Jayme, <jay...@gmail.com> wrote: >> >>> More info from the gdploy config: >>> >>> action=create >>> devices=sda,sdb >>> names=vdo_sda,vdo_sdb >>> logicalsize=17000G,17000G >>> blockmapcachesize=128M >>> readcache=enabled >>> readcachesize=20M >>> emulate512=on >>> writepolicy=auto >>> ignore_vdo_errors=no >>> slabsize=32G,32G >>> >>> >>> action=create >>> devices=sda,sdb >>> names=vdo_sda,vdo_sdb >>> logicalsize=17000G,17000G >>> blockmapcachesize=128M >>> readcache=enabled >>> readcachesize=20M >>> emulate512=on >>> writepolicy=auto >>> ignore_vdo_errors=no >>> slabsize=32G,32G >>> >>> On Tue, Jul 31, 2018 at 4:19 PM, Jayme <jay...@gmail.com> wrote: >>> >>>> PLAY [gluster_servers] ****************************** >>>> *************************** >>>> >>>> TASK [Create VDO with specified size] ****************************** >>>> ************ >>>> failed: [HOST] (item={u'disk': u'/dev/sda', u'logicalsize': u'17000G', >>>> u'name': u'vdo_sda'}) => {"changed": false, "err": "usage: vdo create [-h] >>>> -n <volume> --device <devicepath>\n [--activate >>>> {disabled,enabled}]\n [--blockMapCacheSize <megabytes>]\n >>>> [--blockMapPeriod <period>]\n >>>> [--compression {disabled,enabled}]\n [--deduplication >>>> {disabled,enabled}]\n [--emulate512 {disabled,enabled}] >>>> [--force]\n [--indexMem <gigabytes>] [--readCache >>>> {disabled,enabled}]\n [--readCacheSize <megabytes>]\n >>>> [--sparseIndex {disabled,enabled}]\n >>>> [--vdoAckThreads <threadCount>]\n >>>> [--vdoBioRotationInterval <ioCount>]\n [--vdoBioThreads >>>> <threadCount>]\n [--vdoCpuThreads <threadCount>]\n >>>> [--vdoHashZoneThreads <threadCount>]\n >>>> [--vdoLogicalSize <megabytes>]\n [--vdoLogicalThreads >>>> <threadCount>]\n [--vdoLogLevel >>>> {critical,error,warning,notice,info,debug}]\n >>>> [--vdoPhysicalThreads <threadCount>]\n >>>> [--vdoSlabSize <megabytes>]\n [--writePolicy >>>> {async,sync,auto}] [-f <file>]\n [--logfile <pathname>] >>>> [--verbose]\nvdo create: error: argument --vdoSlabSize: must be an >>>> LVM-style size string\n", "item": {"disk": "/dev/sda", "logicalsize": >>>> "17000G", "name": "vdo_sda"}, "msg": "Creating VDO vdo_sda failed.", "rc": >>>> 2} >>>> failed: [HOST] (item={u'disk': u'/dev/sdb', u'logicalsize': u'17000G', >>>> u'name': u'vdo_sdb'}) => {"changed": false, "err": "usage: vdo create [-h] >>>> -n <volume> --device <devicepath>\n [--activate >>>> {disabled,enabled}]\n [--blockMapCacheSize <megabytes>]\n >>>> [--blockMapPeriod <period>]\n >>>> [--compression {disabled,enabled}]\n [--deduplication >>>> {disabled,enabled}]\n [--emulate512 {disabled,enabled}] >>>> [--force]\n [--indexMem <gigabytes>] [--readCache >>>> {disabled,enabled}]\n [--readCacheSize <megabytes>]\n >>>> [--sparseIndex {disabled,enabled}]\n >>>> [--vdoAckThreads <threadCount>]\n >>>> [--vdoBioRotationInterval <ioCount>]\n [--vdoBioThreads >>>> <threadCount>]\n [--vdoCpuThreads <threadCount>]\n >>>> [--vdoHashZoneThreads <threadCount>]\n >>>> [--vdoLogicalSize <megabytes>]\n [--vdoLogicalThreads >>>> <threadCount>]\n [--vdoLogLevel >>>> {critical,error,warning,notice,info,debug}]\n >>>> [--vdoPhysicalThreads <threadCount>]\n >>>> [--vdoSlabSize <megabytes>]\n [--writePolicy >>>> {async,sync,auto}] [-f <file>]\n [--logfile <pathname>] >>>> [--verbose]\nvdo create: error: argument --vdoSlabSize: must be an >>>> LVM-style size string\n", "item": {"disk": "/dev/sdb", "logicalsize": >>>> "17000G", "name": "vdo_sdb"}, "msg": "Creating VDO vdo_sdb failed.", "rc": >>>> 2} >>>> to retry, use: --limit @/tmp/tmpQQ9t92/vdo-create.retry >>>> >>>> PLAY RECAP ************************************************************ >>>> ********* >>>> HOST : ok=0 changed=0 unreachable=0 failed=1 >>>> >>>> >>> _______________________________________________ >>> Users mailing list -- users@ovirt.org >>> To unsubscribe send an email to users-le...@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/RYW2L5XXTII2FLZKTN6JFO3W3Q63IMAN/ >>> >> > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/D5PPVEYJSARVTM5V535EY6HOYXDGIGJX/ > >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/PBIERKXGGPYO4656CRUJY5HWWR5BKRXR/
