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.
DescriptionSweet Tea Dorminy
2021-08-23 22:30:46 UTC
This bug was initially created as a copy of Bug #1996893
Description of problem:
When VDO is in read-only mode, an attempt to suspend and resume the VDO will fail to resume, leaving data inaccessible.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Start a VDO named vdo0
2. Cause it to go read-only (for instance, by having set it up atop a dm-flakey with the error_writes flag)
3. sudo dmsetup suspend vdo0
4. sudo dmsetup resume vdo0
Actual results:
device-mapper: resume ioctl on vdo0 failed: Input/output error
and in kernel log:
[ 863.423024] kvdo0:dmsetup: resuming device '253:3'
[ 863.428910] kvdo0:dmsetup: resume of device '253:3' failed with error: 1485
[ 863.436369] device-mapper: table: 253:3: vdo: preresume failed, error = -5
Expected results:
(no output, resume succeeds)
Additional info: