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 block map page is more than 16T into a VDO storage device, and the recovery journal has an entry for that block map page, both normal recovery and read-only rebuild will hang indefinitely due to accidental truncation of a 64 bit block number into 32 bits.

Version-Release number of selected component (if applicable):
kmod-kvdo-6.1.0.185-17

How reproducible: Moderately

Steps to Reproduce:
1. Make a >16T physical VDO.
2. Write some data, coercing the block map pages to be at the end of the volume. (I believe the default allocation policy means this happens with any write)
3.Crash and restart the machine.

Actual results:
Infinite hang during restart

Expected results:
Finite-time waiting.

Additional info:

I was not able to reproduce it with vdo-6.1.1.125 using the reproducer in Z-stream clone - creating VDO with 180G index and crashing while randwriting data, the rebuild passed and both VDO devices started without issues.

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-2018:3094