Bug 1794321

Summary: lvcreate break new vdo_format tool with new extended output
Product: Red Hat Enterprise Linux 8 Reporter: Zdenek Kabelac <zkabelac>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
lvm2 sub component: Command-line tools QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, awalsh, cmarthal, heinzm, jbrassow, mcsontos, msnitzer, pasik, prajnoha, rbednar, thornber, zkabelac
Version: 8.2   
Target Milestone: rc   
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lvm2-2.03.08-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:58:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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