Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
DM supports devices consisting of multiple segments. Trying the same with kvdo results in obscure error if the same pool name is used.

# dmsetup create vdo_instance --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo_instance
1000 1000 vdo V2 /dev/sdc 2441609216 4096 32768 16380 off sync vdo_instance"
device-mapper: reload ioctl on vdo_instance  failed: Input/output error
Command failed.

syslog:
[ 9476.234768] device-mapper: table: 253:0: vdo: Starting sector cannot change
[ 9476.241783] device-mapper: ioctl: error adding target to table

Version-Release number of selected component (if applicable):
kmod-kvdo-6.2.1.102-53.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1.dmsetup create vdo_instance --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo_instance
1000 1000 vdo V2 /dev/sdc 2441609216 4096 32768 16380 off sync vdo_instance"

Actual results:
[ 9476.234768] device-mapper: table: 253:0: vdo: Starting sector cannot change

Expected results:
VDO device created or reasonable error given

Additional info:
There has to be an actual newline in the DM table.

kmod-kvdo-6.2.1.138-57.el8.x86_64

# dmsetup create vdo_instance --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo_instance
1000 1000 vdo V2 /dev/sdc 2441609216 4096 32768 16380 off sync vdo_instance"

[13934.406592] kvdo1:dmsetup: WARNING: Running in sync mode atop a device supporting flushes is dangerous!
[13934.469591] device-mapper: table: 253:0: target type vdo must appear alone in table
[13934.477247] device-mapper: ioctl: error adding target to table
[13934.485321] kvdo1:dmsetup: journal being freed has uncommited entries

So now the error message says the target has to be alone in the table.

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-2019:3548