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 1794321 - lvcreate break new vdo_format tool with new extended output
Summary: lvcreate break new vdo_format tool with new extended output
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-23 09:56 UTC by Zdenek Kabelac
Modified: 2021-09-07 11:55 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.03.08-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:58:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-33369 0 None None None 2021-09-07 11:53:19 UTC
Red Hat Product Errata RHEA-2020:1881 0 None None None 2020-04-28 16:59:15 UTC

Description Zdenek Kabelac 2020-01-23 09:56:36 UTC 
Description of problem:

vdo_format extended its output with new info for users (exposing limits for the formated VDO volume).  This change however results into a problem of breaking 'lvcreate --vdo' support as the  lvm2 was just expecting a single line output and after reading that, it closes the pipe and kills the vdo_format command and whole creation of VDO pool fails.

Version-Release number of selected component (if applicable):
lvm  2.03.07

Steps to Reproduce:
1. lvcreate --vdo -L5G vg
Comment 1 Zdenek Kabelac 2020-01-23 09:58:03 UTC 
Fixed with upstream commit:

https://www.redhat.com/archives/lvm-devel/2020-January/msg00038.html
Comment 3 Zdenek Kabelac 2020-02-10 14:46:51 UTC 
The patch needs update - to handle the case when -V is specified with lvcreate line:

https://www.redhat.com/archives/lvm-devel/2020-February/msg00030.html
Comment 5 Roman Bednář 2020-03-18 09:17:46 UTC 
Verified with latest rpms.

# lvcreate --vdo -L5G vg
    Logical blocks defaulted to 522435 blocks.
    The VDO volume can address 2 GB in 4 data slabs, each 512 MB.
    It can grow to address at most 4 TB of physical storage in 8192 slabs.
    If a larger maximum size might be needed, use bigger slabs.
  Logical volume "lvol0" created.

# lvcreate --vdo -L5G -V10G vg
    The VDO volume can address 2 GB in 4 data slabs, each 512 MB.
    It can grow to address at most 4 TB of physical storage in 8192 slabs.
    If a larger maximum size might be needed, use bigger slabs.
  Logical volume "lvol1" created.

# lvs -a
  LV             VG            Attr       LSize   Pool   Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root           rhel_virt-365 -wi-ao----  <6.20g
  swap           rhel_virt-365 -wi-ao---- 820.00m
  lvol0          vg            vwi-a-v---  <1.99g vpool0        0.00
  lvol1          vg            vwi-a-v---  10.00g vpool1        0.00
  vpool0         vg            dwi-------   5.00g               60.08
  [vpool0_vdata] vg            Dwi-ao----   5.00g
  vpool1         vg            dwi-------   5.00g               60.08
  [vpool1_vdata] vg            Dwi-ao----   5.00g



kernel-4.18.0-185.el8    BUILT: Sat Feb 29 00:18:25 CET 2020
lvm2-2.03.08-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
lvm2-libs-2.03.08-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
lvm2-lockd-2.03.08-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
device-mapper-1.02.169-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
device-mapper-libs-1.02.169-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
device-mapper-event-1.02.169-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
device-mapper-event-libs-1.02.169-2.el8    BUILT: Mon Feb 24 18:21:38 CET 2020
device-mapper-persistent-data-0.8.5-3.el8    BUILT: Wed Nov 27 14:05:21 CET 2019
sanlock-lib-3.8.0-2.el8    BUILT: Wed Jun 12 22:50:27 CEST 2019
vdo-6.2.2.117-13.el8    BUILT: Tue Feb 11 17:04:28 CET 2020
kmod-kvdo-6.2.2.117-63.el8    BUILT: Tue Feb 11 17:04:51 CET 2020
Comment 7 errata-xmlrpc 2020-04-28 16:58:59 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, 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/RHEA-2020:1881
Note You need to log in before you can comment on or make changes to this bug.