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 1825344 - LVM changes to dm_path with respect to VDO create volumes make vdo list show incorrect info
Summary: LVM changes to dm_path with respect to VDO create volumes make vdo list show ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: bjohnsto
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-17 18:32 UTC by bjohnsto
Modified: 2021-09-06 15:27 UTC (History)
1 user (show)

Fixed In Version: 6.2.3.22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:01:47 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:57 UTC

Description bjohnsto 2020-04-17 18:32:27 UTC 
Description of problem:

In a recent build of RH 8, we noticed vdo list no longer worked properly. On investigation, we realized changes in lvm dmsetup status calls with the path option caused the issue. 


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


How reproducible:

100%

Steps to Reproduce:
1. Create a VDO volume using LVM
2. Create a VDO volume using VDO manager.
3. Run vdo list from vdo manager. 

Actual results:

Both vdo volumes show up

Expected results:

Only the VDO volume created by VDO manager should show.

Additional info:
Comment 1 Andy Walsh 2020-04-17 19:05:27 UTC 
Here is some output showing the behavior:

[root@localhost ~]# rpm -qa lvm2 device-mapper vdo kmod-kvdo kernel
lvm2-2.03.08-3.el8.x86_64
device-mapper-1.02.169-3.el8.x86_64
kernel-4.18.0-193.8.el8.x86_64
kmod-kvdo-6.2.2.117_8.3-69.el8.x86_64
vdo-6.2.2.117-13.el8.x86_64
[root@localhost ~]# lsblk
NAME   MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda    253:0    0  20G  0 disk
└─vda1 253:1    0  20G  0 part /
[root@localhost ~]# df -h .
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        20G  2.2G   18G  11% /
[root@localhost ~]# truncate -s 9g loop0
[root@localhost ~]# truncate -s 9g loop1
[root@localhost ~]# losetup loop0 loop0
[root@localhost ~]# losetup loop1 loop1
[root@localhost ~]# vdo create --name vdo0 --device /dev/loop0
Creating VDO vdo0
      Logical blocks defaulted to 1569686 blocks.
      The VDO volume can address 6 GB in 3 data slabs, each 2 GB.
      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.
Starting VDO vdo0
Starting compression on VDO vdo0
VDO instance 0 volume is ready at /dev/mapper/vdo0
[root@localhost ~]# lvcreate -L 8G -V 100G  ^C
[root@localhost ~]# vgcreate vg /dev/loop1                                                                                                                                                                                                                                                                                    
  Volume group "vg" successfully created
[root@localhost ~]# lvcreate -L 8G -V 100G --type vdo vg/vdopool
    The VDO volume can address 5 GB in 10 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.
[root@localhost ~]# vdo list
vdo0
vg-vdopool-vpool
Comment 4 Filip Suba 2020-08-20 13:20:56 UTC 
Verified with vdo-6.2.3.114-14.el8.

# vdo create --name vdo0 --device /dev/sda
Creating VDO vdo0
      Logical blocks defaulted to 1569686 blocks.
      The VDO volume can address 6 GB in 3 data slabs, each 2 GB.
      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.
Starting VDO vdo0
Starting compression on VDO vdo0
VDO instance 0 volume is ready at /dev/mapper/vdo0
# vgcreate vg2 /dev/loop2
  Physical volume "/dev/loop2" successfully created.
  Volume group "vg2" successfully created
# lvcreate -L 8G -V 100G --type vdo vg2/vdopool
    The VDO volume can address 4 GB in 2 data slabs, each 2 GB.
    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.
# vdo list
vdo0
Comment 7 errata-xmlrpc 2020-11-04 02:01:47 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.