Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1986595

Summary: vdo2lvm "Retrying in use check" messages seems excessive
Product: Red Hat Enterprise Linux 8 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: sclafani
lvm2 sub component: VDO QA Contact: Filip Suba <fsuba>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: high CC: agk, awalsh, fsuba, heinzm, jbrassow, prajnoha, zkabelac
Version: 8.5Keywords: Triaged
Target Milestone: betaFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kmod-kvdo-6.2.7.5-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-08 10:55:24 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 Corey Marthaler 2021-07-27 20:28:32 UTC 
Description of problem:

[root@hayes-01 ~]# vdo2lvm /dev/snapper_thinp/origin 
Opening /dev/snapper_thinp/origin exclusively
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
vdo2lvm: Failed to open '/dev/snapper_thinp/origin' exclusively : Device or resource busy

[root@hayes-01 ~]# umount /mnt/origin 

[root@hayes-01 ~]# vdo2lvm /dev/snapper_thinp/origin 
Opening /dev/snapper_thinp/origin exclusively
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
Retrying in use check for /dev/snapper_thinp/origin.
vdo2lvm: Failed to open '/dev/snapper_thinp/origin' exclusively : Device or resource busy

[root@hayes-01 ~]# vdo remove -n origin
Removing VDO origin
Stopping VDO origin

Version-Release number of selected component (if applicable):
kernel-4.18.0-323.el8    BUILT: Wed Jul 14 12:12:22 CDT 2021
lvm2-2.03.12-5.el8    BUILT: Tue Jul 13 11:50:03 CDT 2021
lvm2-libs-2.03.12-5.el8    BUILT: Tue Jul 13 11:50:03 CDT 2021
vdo-6.2.5.41-14.el8    BUILT: Tue Jun  1 19:04:22 CDT 2021
kmod-kvdo-6.2.5.41-79.el8    BUILT: Tue Jun 22 10:14:43 CDT 2021


How reproducible:
Everytime
Comment 6 Corey Marthaler 2022-07-27 21:11:06 UTC 
Fix verified in the latest rpms.

kernel-4.18.0-411.el8    BUILT: Wed Jul 20 18:42:42 CDT 2022

vdo-6.2.6.14-14.el8    BUILT: Fri Feb 11 14:43:08 CST 2022
kmod-kvdo-6.2.7.17-86.el8    BUILT: Mon Jul 18 17:07:57 CDT 2022

lvm2-2.03.14-5.el8    BUILT: Thu Jul 14 09:23:13 CDT 2022
lvm2-libs-2.03.14-5.el8    BUILT: Thu Jul 14 09:23:13 CDT 2022



[root@hayes-01 ~]# lvs -a -o +devices
  LV    VG   Attr       LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert Devices     
  lvol0 test -wi-ao---- 8.00g                                                     /dev/sdc1(0)
[root@hayes-01 ~]# vdo list
vdo
[root@hayes-01 ~]# mount /dev/mapper/vdo /mnt

[root@hayes-01 ~]# vdo2lvm /dev/mapper/vdo
bash: vdo2lvm: command not found...

[root@hayes-01 ~]# lvm_import_vdo /dev/test/lvol0 
lvm_import_vdo: Cannot convert in use VDO volume "vdo"!
[root@hayes-01 ~]# lvm_import_vdo /dev/mapper/vdo
lvm_import_vdo: Can't find matching device in vdo configuration file.
Comment 8 errata-xmlrpc 2022-11-08 10:55:24 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 (lvm2 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-2022:7792