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.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/storage_administration_guide/index

Section Number and Name: 
29.3.3. Creating a VDO Volume

Describe the issue: 
XFS and EXT4 examples should be updated from
  "x-systemd.requires=vdo.service 0 0"



Suggestions for improvement: 

to
  "_netdev,x-systemd.device-timeout=0,x-systemd.requires=vdo.service"

Additional information:

(In reply to Dennis Keefe from comment #0)
> Document URL: 
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/
> html-single/storage_administration_guide/index
> 
> Section Number and Name: 
> 29.3.3. Creating a VDO Volume
> 
> Describe the issue: 
> XFS and EXT4 examples should be updated from
>   "x-systemd.requires=vdo.service 0 0"
> 
> 
> 
> Suggestions for improvement: 
> 
> to
>   "_netdev,x-systemd.device-timeout=0,x-systemd.requires=vdo.service"
> 
> Additional information:

I've fixed the mount options both in RHEL 7 and RHEL 8 Beta documentation. I assume the same edit was needed in both versions. Previews:

* 7: https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-quick-start#vdo-qs-creating-a-volume

* 8 Beta: https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/deduplicating_and_compressing_storage/assembly_getting-started-with-vdo-deduplicating-and-compressing-storage#proc_creating-a-vdo-volume-getting-started-with-vdo

Is this correct now? If so, I'll republish the docs.

I notice the RHEL 7 procedure also suggests creating a systemd mount unit as an alternative to fstab. Do any of the new options need to be added there as well?

*** Bug 1655781 has been marked as a duplicate of this bug. ***

In our email conversation, we've agreed that the issue is now solved, so I'm closing this bug.