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.
Bug 1746539 - VDO man page does not provide guidance for mounting a VDO volume
Summary: VDO man page does not provide guidance for mounting a VDO volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Sweet Tea Dorminy
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 17:41 UTC by Andy Walsh
Modified: 2021-09-06 15:22 UTC (History)
1 user (show)

Fixed In Version: 6.2.2.116
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:43:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-32705 0 None None None 2021-09-06 15:22:45 UTC
Red Hat Product Errata RHBA-2020:1782 0 None None None 2020-04-28 16:43:21 UTC

Description Andy Walsh 2019-08-28 17:41:31 UTC
Description of problem:
The 'vdo' manpage does not provide guidance for what is needed to use a VDO volume as the backing device for a filesystem in the /etc/fstab.  There is an example systemd mount unit provided at /usr/share/doc/vdo/examples, but again, there is no guidance on how or when to use it.

Version-Release number of selected component (if applicable):
Everything up to vdo-6.2.1.134

Expected results:
We should provide guidance to have the user either use mount options (x-systemd.requires=vdo.service) in the fstab or to use the provided systemd mount unit file. when attempting to have a VDO volume mount at boot time.

Comment 1 Jakub Krysl 2019-10-15 14:38:54 UTC
Mass migration to Filip.

Comment 4 Filip Suba 2020-03-11 09:26:53 UTC
Verified with vdo-6.2.2.117-13.el8.

Comment 6 errata-xmlrpc 2020-04-28 16:43:10 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, 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:1782


Note You need to log in before you can comment on or make changes to this bug.