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:
When creating VDO without using --vdoLogicalSize, the logical size in vdo status is smaller than available size in vdostats on newly created VDO:

# vdo create --name vdo --device /dev/sdc
# vdo status | grep "Physical size"
    Physical size: 5860522584K

# vdostats
Device               1K-blocks      Used Available Use% Space saving%
/dev/mapper/vdo      5860522584   7131936 5853390648   0%           N/A
# vdo status | grep "Logical size"
    Logical size: 5846172208K

Version-Release number of selected component (if applicable):
vdo-6.1.0.98-13
kmod-kvdo-6.1.0.98-11

How reproducible:
100%

Steps to Reproduce:
1. vdo create --name vdo --device /dev/sdc
2. vdostats
3. vdo status | grep "Logical size"
4. compare vdo status "Logical size" and vdostats "Available" size

Actual results:
vdostats "Available" size is bigger

Expected results:
both sizes are the same

Additional info:

As per discussion we decided to treat this as docs bug, as changing what this counter represents could lead to much bigger issues. Now the "available" 1-K blocks counter does not represent actual counter of 1-K blocks usable by user, but number of 1-K blocks usable by the VDO itself. These uses include not only user data but also managing data for said user data.

The documentation now states this regarding the counter:
Available
              The total number of 1K blocks available on a VDO volume (= physical blocks free *  block size / 1024)

This docs field should better reflect the fact stated above to avoid future confusion why writing X 1K blocks to VDO reduces this counted by >X.

Mass migration to Filip.

This has been fixed for some time now.