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 1944087 - [RFE] print warning when multiple "--device=" options are used to create vdo device
Summary: [RFE] print warning when multiple "--device=" options are used to create vdo ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: bjohnsto
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-29 09:14 UTC by Rupesh Girase
Modified: 2021-11-10 06:38 UTC (History)
3 users (show)

Fixed In Version: vdo-6.2.5.11-14.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:28:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4359 0 None None None 2021-11-09 19:28:38 UTC

Description Rupesh Girase 2021-03-29 09:14:53 UTC 
Description of problem:
print warning when multiple "--device=" options are used to create vdo device as it uses one block device only 

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

How reproducible:


Steps to Reproduce:

o Create vdo with multiple --device options
   
used these two block devices
nvme0n6                        259:7    0  74.5G  0 disk 
nvme0n7                        259:8    0  74.5G  0 disk 


# vdo create --name=multivdo --device=/dev/nvme0n6 --device=/dev/nvme0n7 --vdoSlabSize=256M 
Creating VDO multivdo
      Logical blocks defaulted to 18716406 blocks.
      The VDO volume can address 71 GB in 287 data slabs, each 256 MB.
      It can grow to address at most 2 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO multivdo
Starting compression on VDO multivdo
VDO instance 3 volume is ready at /dev/mapper/multivdo




Actual results:
Creates vdo volume with one block device only and does not tell anything about other one

Expected results:
warning should be printed saying other device is ignored or not used

Additional info:
Comment 5 Filip Suba 2021-05-27 13:19:17 UTC 
Verified with vdo-6.2.5.11-14.el8.
# vdo create -n vdo --device /dev/sdc --device /dev/sdd
usage: vdo create [-h] -n <volume> --device <devicepath>
                  [--activate {disabled,enabled}]
                  [--blockMapCacheSize <megabytes>]
                  [--blockMapPeriod <period>]
                  [--compression {disabled,enabled}]
                  [--deduplication {disabled,enabled}]
                  [--emulate512 {disabled,enabled}] [--force]
                  [--indexMem <gigabytes>] [--maxDiscardSize <megabytes>]
                  [--sparseIndex {disabled,enabled}] [--uuid <uuid>]
                  [--vdoAckThreads <threadCount>]
                  [--vdoBioRotationInterval <ioCount>]
                  [--vdoBioThreads <threadCount>]
                  [--vdoCpuThreads <threadCount>]
                  [--vdoHashZoneThreads <threadCount>]
                  [--vdoLogicalSize <megabytes>]
                  [--vdoLogicalThreads <threadCount>]
                  [--vdoLogLevel {critical,error,warning,notice,info,debug}]
                  [--vdoPhysicalThreads <threadCount>]
                  [--vdoSlabSize <megabytes>]
                  [--writePolicy {async,async-unsafe,sync,auto}] [-f <file>]
                  [--logfile <pathname>] [--verbose]
vdo create: error: option 'device' was specified more than once
Comment 8 errata-xmlrpc 2021-11-09 19:28:28 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 (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-2021:4359
Note You need to log in before you can comment on or make changes to this bug.