+++ This bug was initially created as a clone of Bug #1723728 +++ 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
Note: QE validation of 4KN device support is still under testing, and this can be completed only by mid of July. So please proceed with the fix, only after QE acks the 4KN support works
As per RHHI-V Pgm call on 07-Aug, re-targeting this bug to RHV 4.3.7 as 4KN support had other issues to be solved
The dependent bug is ON_QA and moving this bug too to ON_QA
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>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0508