Bug 1996893

Summary:	VDO resume in read only mode never succeeds.
Product:	Red Hat Enterprise Linux 8	Reporter:	Sweet Tea Dorminy <sweettea>
Component:	kmod-kvdo	Assignee:	corwin <corwin>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.7	CC:	awalsh, corwin, cwei, fsuba
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kmod-kvdo-6.2.6.3-82.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2004206 (view as bug list)		Environment:
Last Closed:	2022-05-10 15:17:21 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:
Bug Depends On:
Bug Blocks:	2004206

Description Sweet Tea Dorminy 2021-08-23 22:28:24 UTC

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:

Comment 5 Filip Suba 2021-11-22 14:14:42 UTC

Verified with kmod-kvdo-6.2.6.3-82.el8.

Comment 7 errata-xmlrpc 2022-05-10 15:17:21 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-2022:2003