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:

When VDO encounters an unrecoverable error, it enters read-only mode. Any write requests which are in progress once VDO has entered read-only mode should be failed with a VDO_READ_ONLY error. 

However, the VDO kernel module uses a number of threads, and the notification that the device has gone read-only can race with the clean up of failed write requests, causing them log a spurious error of the form:
 "VDO not read-only when cleaning DataVIO with RJ lock"

While there is no actual problem, this could cause confusion for customers and unnecessary support calls.

Version-Release number of selected component (if applicable):


How reproducible:

Difficult

Steps to Reproduce:
1. Initiate writing to a VDO
2. Cause the VDO to enter read-only mode while writes are in progress, for example by introducing an I/O error from the underlying storage.
3. Observe log message of the form described above after the appearance of the log message indicating the IO error.

Actual results:

After an I/O error from the underlying storage, VDO logs errors of the form "VDO not read-only when cleaning DataVIO with RJ lock" 

Expected results:

VDO does not log such errors after an I/O error.

Additional info:

Verified SanityOnly. Regression testing passed.

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-2020:4551