Bug 1629542
| Summary: | The LV size should be equal to the logical size on VDO enabled volumes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | bipin <bshetty> | ||||
| Component: | rhhi | Assignee: | Gobinda Das <godas> | ||||
| Status: | CLOSED ERRATA | QA Contact: | bipin <bshetty> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | rhhiv-1.5 | CC: | godas, guillaume.pavese, rcyriac, rhs-bugs, sabose, sankarshan, sasundar | ||||
| Target Milestone: | --- | ||||||
| Target Release: | RHHI-V 1.6 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, the logical size of a VDO volume was 10 times the size of the brick by default. This meant that using the default settings wasted storage space. The default size of the brick and the default logical size of the VDO volume are now the same.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1629543 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-05-09 06:09:23 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1629543 | ||||||
| Bug Blocks: | 1672930 | ||||||
| Attachments: |
|
||||||
Sahina, As discussed in the engineering bi-weekly meeting today, the LV size will be made up to the logical size of VDO. Are you ok with fixing this for RHV 4.2.7 (i.e) RHHI 2.0. In that case please provide devel_ack on this bug Please provide doc_text Verified the bug on the latest cockpit dashboard and could see the LV size is equal to the logical size of VDO volume Components version: ================== cockpit-ovirt-dashboard-0.12.5-1.el7ev.noarch rhvh-4.3.0.5-0.20190313.0+1 Steps: ===== 1. Check the VDO box for the brick you want to have dedupe and compression enabled 2. Once deployed compare the size of the LV and VDO logical size Could see that the ansible playbook generated in the review tab had proper values set. Output: ====== sdb 8:16 0 20T 0 disk └─vdo_sdb 253:12 0 80T 0 vdo ├─gluster_vg_sdb-gluster_lv_data 253:14 0 40T 0 lvm /gluster_bricks/data └─gluster_vg_sdb-gluster_lv_vmstore 253:15 0 40T 0 lvm /gluster_bricks/vmstore [root@rhsqa-abc log]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert gluster_lv_data gluster_vg_sdb -wi-ao---- 40.00t gluster_lv_vmstore gluster_vg_sdb -wi-ao---- <40.00t Moving to verified based on above result 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/RHEA-2019:1121 |
Created attachment 1483854 [details] UI_Screenshot Description of problem: In currently implementation,the LV size is always lesser than the logical size while creating the VDO volumes. Going forward the LV should be equal to the logical size to fully utilize the underline storage. Version-Release number of selected component (if applicable): cockpit-ovirt-dashboard-0.11.33-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: The LV size is lesser than logical size Expected results: The LV size should be equal to logical size Additional info: Adding the screenshot from the cockpit UI