Bug 2176778 - Update vdo support tools help messages to reflect VDO integration to LVM
Summary: Update vdo support tools help messages to reflect VDO integration to LVM
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: vdo
Version: 9.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: sclafani
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-09 09:45 UTC by Filip Suba
Modified: 2023-07-17 17:48 UTC (History)
3 users (show)

Fixed In Version: vdo-8.2.2.2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-151197 0 None None None 2023-03-09 09:47:01 UTC

Description Filip Suba 2023-03-09 09:45:18 UTC
Description of problem:
After change to LVM it might be harder for a user to determine "<vdoBacking>" or "<device>". Help pages of vdo support tools should be updated with an explanation of what to use as a <device> when using LVM to create a VDO volume.

Version-Release number of selected component (if applicable):
vdo-8.2.0.2-1.el9
vdo-support-8.2.0.2-1.el9

How reproducible:
100%

Steps to Reproduce:
1. vdodumpconfig --help
2.
3.

Actual results:
vdodumpconfig - dump the configuration of a VDO volume from its backing
                store.

SYNOPSIS
  vdodumpconfig <vdoBacking>

DESCRIPTION
  vdodumpconfig dumps the configuration of a VDO volume, whether or not
  the VDO is running.
OPTIONS
    --help
       Print this help message and exit.

    --version
       Show the version of vdodmeventd.

Expected results:
Add an example of how to use it with LVMVDO (vdodumpconfig /dev/mapper/vg-vpool0_vdata) and add an explanation that vdodumpconfig should be used with /dev/mapper/*VG-VPOOL*_vdata. 


Additional info:

Comment 6 Filip Suba 2023-07-17 17:48:25 UTC
Verified with vdo-8.2.2.2-1.el9.


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