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.
Description of problem:
If a VDO volume is created on a device, and that VDO volume is stopped, and the device is later removed from the system (perhaps because the VDO volume is not needed anymore, but the administrator forgot to run the "vdo remove" command prior to removing the backing storage device), a zero-byte regular file will be created with the same name of the device previously used to create the now-removed VDO volume.
Version-Release number of selected component (if applicable):
vdo-6.1.0.98-13.x86_64
How reproducible:
100% so far
Steps to Reproduce:
1. Create a VDO volume on a test device (example: /dev/sdb) using the command "vdo create --name=vdo1 --device=/dev/sdb".
2. Stop the VDO volume using the command "vdo stop --name=vdo1".
3. Remove the backing device from the system
4. Run "vdo remove --name=vdo1 --verbose".
Actual results:
The VDO volume is successfully removed, but a zero-byte regular file is left over in the path of the previous backing device:
# vdo remove --name=vdo1 --verbose
Removing VDO vdo1
Stopping VDO vdo1
dmsetup status vdo1
dd if=/dev/zero of=/dev/sdb oflag=direct bs=4096 count=1
vdo: ERROR - dd: failed to open ‘/dev/sdb’: Invalid argument
# ls -l /dev/sdb
-rw-r--r--. 1 root root 0 Jan 2 13:08 /dev/sdb
# vdo remove --name=vdo1 --verbose
vdo: ERROR - VDO volume vdo1 not found
Expected results:
The VDO volume is successfully removed. No device file is created if it doesn't already exist.
Additional info:
If this regular file still exists, and the device (or another device) is reattached to the system without removing the zero-byte regular file, it will result in the failure to create a node for the device. (This can be worked around by removing the zero-byte regular file, and running mknod to recreate it, or rebooting the system.)
Fixed with change 132391, merged as change 132632.
The bug was caused by a cleanup routine that zeros the first block of a vdo device on remove to prevent accidental re-use. The fix checks to make sure there's still a device present and skips the zeroing step if the device is missing.
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-2018:0871
Description of problem: If a VDO volume is created on a device, and that VDO volume is stopped, and the device is later removed from the system (perhaps because the VDO volume is not needed anymore, but the administrator forgot to run the "vdo remove" command prior to removing the backing storage device), a zero-byte regular file will be created with the same name of the device previously used to create the now-removed VDO volume. Version-Release number of selected component (if applicable): vdo-6.1.0.98-13.x86_64 How reproducible: 100% so far Steps to Reproduce: 1. Create a VDO volume on a test device (example: /dev/sdb) using the command "vdo create --name=vdo1 --device=/dev/sdb". 2. Stop the VDO volume using the command "vdo stop --name=vdo1". 3. Remove the backing device from the system 4. Run "vdo remove --name=vdo1 --verbose". Actual results: The VDO volume is successfully removed, but a zero-byte regular file is left over in the path of the previous backing device: # vdo remove --name=vdo1 --verbose Removing VDO vdo1 Stopping VDO vdo1 dmsetup status vdo1 dd if=/dev/zero of=/dev/sdb oflag=direct bs=4096 count=1 vdo: ERROR - dd: failed to open ‘/dev/sdb’: Invalid argument # ls -l /dev/sdb -rw-r--r--. 1 root root 0 Jan 2 13:08 /dev/sdb # vdo remove --name=vdo1 --verbose vdo: ERROR - VDO volume vdo1 not found Expected results: The VDO volume is successfully removed. No device file is created if it doesn't already exist. Additional info: If this regular file still exists, and the device (or another device) is reattached to the system without removing the zero-byte regular file, it will result in the failure to create a node for the device. (This can be worked around by removing the zero-byte regular file, and running mknod to recreate it, or rebooting the system.)