+++ This bug was initially created as a clone of Bug #1568997 +++
Description of problem:
Currently the Logical size for VDO is 10 times the sum of all bricks created. But the logical size should always be 10 times of the physical size of device.
If the device /dev/sdb has a size of the of 20T. Then the logical size should be 200T. This should be irrespective of the brick size selected for each volume.
Also considering a scenario where, if the device size is 20 TB and a volume created out of it is 1T then the logical size will be 10T. Which is less than the physical size. (physical size 20TB > logical size 10 T). This is not recommended according to VDO.
This also eliminates the work of adding the logical size every time we create a new volume.
NOTE: Also had previously confirmed the same with Dennis Keefe. Please find the comment below:
2. vdoLogicalSize = 10 x ( Disk physical size )
In actual, the cockpit implementation does 4 x size of physical disk.
I read from the RHEL 7.5 storage admin guide, about the recommendation of 10:1
The cockpit implementation will allow much large size, though you have to manually change the settings.
10x is typical for VMs. I agree with this setting.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to cockpit UI
2. Start gluster deployment
3. Select the enable compression and dedupe check
Can the VDO volume be resized post creation?
I do see that vdo supports increasing logical volume size and physical volume size as per https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-ig-administering-vdo
Bipin, can you try this out?
The logical size expansion is working. Lowering the severity.
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.
Gobinda, do we plan to address this?
Now the problem is to get device details from remote hosts in cockpit. Will need to try and find a way to get device details of other nodes.Then only will be able to fix this. I tried sometimes back using ansible playbook, but did not work. Will try again. I think we should move this to 4.4 as the logical size is editable and user can give exact value during deployment.
As same device may use to create bricks we can't really determine what is the actual size of device. Cockpit will be accessing from one host and we need to get other hosts device info as well which is not possible from cockpit. So closing this bug.