Description of problem: ----------------------- VDO works as 512e device as 4KN support was not available earlier. 4KN support will be available with the latest sanlock package and now the VDO option to emulate 512 byte device, can be safely removed. Version-Release number of selected component (if applicable): ------------------------------------------------------------- cockpit-ovirt-dashboard-0.13.2 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Remove the VDO option to emulate 512 Actual results: ---------------- VDO has an option to emulate 512 Expected results: ----------------- VDO need not emulate 512
This bug had to be targeted to RHV 4.3.7, as there are other issues with 4KN support and so VDO had be still do 512e
As discussed in RHHI-V Program meeting, support for 4KN devices are planned for RHV 4.3.8 Targeting this bug for RHV 4.3.8
I see that all the patches are merged. But still this bug is on MODIFIED state ? Why was there no new build made for cockpit-ovirt-dashboard ? @sandro, can you help ?
We need a build here. I'll ask Gal to do one.
Tested with cockpit-ovirt-dashboard-0.13.9 When the gluster-inventory.yml file is generated with VDO enabled, emulate512 is set to 'off' <snip> - name: vdo_sdc device: /dev/sdc slabsize: 32G logicalsize: 5000G blockmapcachesize: 128M readcache: enabled readcachesize: 20M emulate512: 'off' writepolicy: auto </snip>
This bugzilla is included in oVirt 4.3.8 release, published on January 27th 2020. Since the problem described in this bug report should be resolved in oVirt 4.3.8 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.