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.
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/RHBA-2020:1105
Description of problem: VDOManager incorrectly takes the wrong /dev/disk/by-id/ path (e.g. the PV path) instead of the original disk path when changing path to persistent. This causes issues later in the process and fail. Running the same command again passes. # pvcreate /dev/sda Physical volume "/dev/sda" successfully created. # hexdump -C /dev/sda -n 4k 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 4c 41 42 45 4c 4f 4e 45 01 00 00 00 00 00 00 00 |LABELONE........| 00000210 f0 5d b8 e6 20 00 00 00 4c 56 4d 32 20 30 30 31 |.].. ...LVM2 001| 00000220 4d 49 6b 39 50 53 6a 61 76 4e 47 34 62 57 55 5a |MIk9PSjavNG4bWUZ| 00000230 6c 39 73 56 62 30 4a 73 6b 5a 5a 76 63 77 56 54 |l9sVb0JskZZvcwVT| 00000240 00 00 00 80 18 09 00 00 00 00 10 00 00 00 00 00 |................| 00000250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000260 00 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 |................| 00000270 00 f0 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000280 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 |................| 00000290 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00001000 # vdo create --name vdo --device /dev/sda --verbose mkdir -p /run/lock/vdo touch /run/lock/vdo/_etc_vdoconf.yml.lock chmod 644 /run/lock/vdo/_etc_vdoconf.yml.lock touch /run/lock/vdo-config-singletons Creating VDO vdo grep MemAvailable /proc/meminfo pvcreate --config devices/scan_lvs=1 -qq --test /dev/sda blkid -p /dev/sda vdo: ERROR - device is a physical volume; use --force to override # vdo create --name vdo --device /dev/sda --verbose --force Creating VDO vdo grep MemAvailable /proc/meminfo modprobe kvdo vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --force /dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT vdo r vdodumpconfig /dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT Removing VDO vdo vdo: ERROR - vdodumpconfig: Failed to make FileLayer from '/dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT' with No such file or directory # hexdump -C /dev/sda -n 4k 00000000 64 6d 76 64 6f 30 30 31 05 00 00 00 04 00 00 00 |dmvdo001........| 00000010 00 00 00 00 5d 00 00 00 00 00 00 00 09 01 02 00 |....]...........| 00000020 f5 b9 5f d0 ac 87 05 00 b2 c4 7b 12 6a 7b 44 af |.._.......{.j{D.| 00000030 85 b5 cd 6e 19 3f 24 0b 00 00 00 00 01 00 00 00 |...n.?$.........| 00000040 00 00 00 00 01 00 00 00 d8 5c 0a 00 00 00 00 00 |.........\......| 00000050 00 ff ff ff 00 00 00 00 00 34 c9 4a 56 00 00 00 |.........4.JV...| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00001000 Version-Release number of selected component (if applicable): kernel-3.10.0-1040.el7.x86_64 vdo-6.1.2.41-4.el7.x86_64 kmod-kvdo-6.1.2.41-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. pvcreate /dev/sda 2. vdo create --name vdo --device /dev/sda --verbose --force Actual results: vdo: ERROR - vdodumpconfig: Failed to make FileLayer from '/dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT' with No such file or directory Expected results: VDO created on 1st try Additional info: