Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
There is no indication newly created VDO may be thinly provisioned, so user might be not aware of it as of now the default VDO is thinly provisioned. For comparision this is how LVM handles it:
# lvcreate -n pool -T -L 2G vg
Using default stripesize 64.00 KiB.
Thin pool volume with chunk size 64.00 KiB can address at most 15.81 TiB of data.
Logical volume "pool" created.
# lvcreate -n lv -T -V 6G vg/pool
Using default stripesize 64.00 KiB.
WARNING: Sum of all thin volume sizes (6.00 GiB) exceeds the size of thin pool vg/pool (2.00 GiB).
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
Logical volume "lv" created.
Version-Release number of selected component (if applicable):
vdo-6.1.0.55-9
How reproducible:
100%
Steps to Reproduce:
1. # vdo create --name vdo --device device
2. check that vdo logical size is greater than vdo slab_size*slab_count (e.g. actual physical size)
# vdo status
Actual results:
No warning
Expected results:
warning similar to 'WARNING: Sum of all thin volume sizes (6.00 GiB) exceeds the size of thin pool vg/pool (2.00 GiB).'
Additional info:
The warning from LVM is not a warning about thin provisioning, but rather a warning that a thinly provisioned volume has been created without enabling overfilling protection. Since there is no overfilling protection to be enabled for VDO, there is nothing to warn about.
We don't want to warn just that the user has created a thinly provisioned volume since that is a perfectly normal thing to do. We don't want to give the user the impression that they've done something wrong.