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.
Bug 1683945 - [RFE] lvm should hint on minimal native vdo volume size
Summary: [RFE] lvm should hint on minimal native vdo volume size
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: bjohnsto
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-28 07:57 UTC by Roman Bednář
Modified: 2021-09-06 15:25 UTC (History)
9 users (show)

Fixed In Version: 6.2.3.97
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:01:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4551 0 None None None 2020-11-04 02:01:46 UTC

Description Roman Bednář 2019-02-28 07:57:35 UTC 
There is minimal size for vdo volume as such (non-native) and if the size is below 
minimum vdo exits with “Out of space” error.
 
It would enhance user experience if lvm would 
hint on the minimal native vdo size instead of “command failed” message.


Current behaviour:

# lvcreate --type vdo -L2G -y vg
vdoformat: formatVDO failed on '/dev/vg/vpool0': VDO Status: Out of space
  Command /usr/bin/vdoformat failed.
  Cannot format VDO pool volume vg/vpool0.

# lvcreate --type vdo -L3G -y vg
vdoformat: formatVDO failed on '/dev/vg/vpool0': VDO Status: Out of space
  Command /usr/bin/vdoformat failed.
  Cannot format VDO pool volume vg/vpool0.

# lvcreate --type vdo -L4G -y vg
  Logical volume "lvol0" created.



Suggestion:

# lvcreate --type vdo -L3G -y vg
    Minimal size of vdo volume is 4G.

# lvcreate -v --type vdo -L3G -y vg
vdoformat: formatVDO failed on '/dev/vg/vpool0': VDO Status: Out of space
  Command /usr/bin/vdoformat failed.
  Cannot format VDO pool volume vg/vpool0.
  Minimal size of vdo volume is 4G.
Comment 1 Jonathan Earl Brassow 2019-03-06 14:30:47 UTC 
Bruce, would you be willing to take a stab at a patch for this?
Comment 3 Andy Walsh 2020-05-15 17:35:27 UTC 
Since this is more of a 'vdoformat' utility change, I'm moving the bug to the vdo component.
Comment 7 Roman Bednář 2020-07-10 07:13:52 UTC 
Verified with latest rpms, VDO now hints users what the min size should be in bytes.

# lvcreate --type vdo -L4.70g vg
  Rounding up size to full physical extent 4.70 GiB
Minimum required size for VDO volume: 5063921664 bytes
vdoformat: formatVDO failed on '/dev/vg/vpool0': VDO Status: Out of space
  Command /usr/bin/vdoformat failed.
  Cannot format VDO pool volume vg/vpool0.

# lvcreate --type vdo -L4.72g vg
  Rounding up size to full physical extent 4.72 GiB
    Logical blocks defaulted to 523108 blocks.
    The VDO volume can address 2 GB in 1 data slab.
    It can grow to address at most 16 TB of physical storage in 8192 slabs.
    If a larger maximum size might be needed, use bigger slabs.
  Logical volume "lvol0" created.

# rpm -qa | egrep "lvm2|vdo" | sort
kmod-kvdo-6.2.3.107-73.el8.x86_64
lvm2-2.03.09-3.el8.x86_64
lvm2-libs-2.03.09-3.el8.x86_64
lvm2-lockd-2.03.09-3.el8.x86_64
vdo-6.2.3.107-14.el8.x86_64
Comment 10 errata-xmlrpc 2020-11-04 02:01:16 UTC 
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 (kmod-kvdo bug fix and enhancement update), 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/RHBA-2020:4551
Note You need to log in before you can comment on or make changes to this bug.