+++ This bug was initially created as a clone of Bug #1547674 +++ Description of problem: ----------------------- VDO volumes comprises of slabs, with default slabsize of 2G. Also there is known limitation of 8096 number of slabs available per VDO volume. So 8096 x 2G = 16TB. In case the physical storage space exceeds 16TB, VDO volume creation fails. So, in this case, the slab size should be increased to a value greater than 2G, and that will decrease the number of slabs. Version-Release number of selected component (if applicable): -------------------------------------------------------------- cockpit-ovirt-dashboard-0.11.11 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Start installation of RHHI 1.1, using 'Hosted Engine with Gluster' option 2. Have a disk with more than 16TB, for the creation of bricks 3. Enable dedupe & compression on that device Actual results: ---------------- VDO volume creation fails with error 'Exceeds maximum number of slabs supported' when the device more than 16TB physical storage space is provided Expected results: ----------------- VDO volume creation should be successful even when the device with more than 16TB is used for bricks In other case, cockpit-ovirt gluster plugin should have that intelligence to increase the slab size in that case when the physical storage space of the device is more than 16TB Additional info: ---------------- I don't have much information about the effect of increasing the slabsize, it needs to be discussed with SME
Handled by existing patch http://gerrit.ovirt.org/88681
Slab size is adjusted based on the logical size of the VDO volume, which is incorrect. Slab size should be determined based on the physical size of the disk.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
4.2.2 was released - please re-target.
Discussed with sas and sahina, right now there is no way to fetch any device informations in cockpit.So we need more discussion and R&D to find the solution that how we can fetch device details from node and parse it to make it visible in cockpit UI.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
This is not possible to fetch device informations from other nodes in cockpit. In this case user need to edit inventory file in cockpit and change accordingly. So closing this bug.