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:
As subject says, creating VDO with only 1 of those options specified leads to VDO actually trying to create it and device-mapper catching the error.
# vdo create --device /dev/sdc --name vdo --verbose --vdoLogicalThreads 0
Creating VDO vdo
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdc
vdodumpconfig /dev/sdc
Starting VDO vdo
dmsetup status vdo
modprobe kvdo
dmsetup create vdo --table '0 11721045168 dedupe /dev/sdc 4096 disabled 0 32768 16380 on sync vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=0,physical=1'
vdo: ERROR - Could not set up device mapper for vdo
Removing VDO vdo
Stopping VDO vdo
dmsetup status vdo
vdo: ERROR - device-mapper: reload ioctl on vdo failed: Invalid argument
console:
[B[22976.417374] device-mapper: table: 253:2: dedupe: Logical, physical, and hash zones counts must all be zero or all non-zero
[22976.428426] device-mapper: ioctl: error adding target to table
# vdo create --device /dev/sdc --name vdo --verbose --vdoPhysicalThreads 0
Creating VDO vdo
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdc
vdodumpconfig /dev/sdc
Starting VDO vdo
dmsetup status vdo
modprobe kvdo
dmsetup create vdo --table '0 11721045168 dedupe /dev/sdc 4096 disabled 0 32768 16380 on sync vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=0'
vdo: ERROR - Could not set up device mapper for vdo
Removing VDO vdo
Stopping VDO vdo
dmsetup status vdo
vdo: ERROR - device-mapper: reload ioctl on vdo failed: Invalid argument
[root@storageqe-24 raid]#
console:
[23218.818914] device-mapper: table: 253:2: dedupe: Logical, physical, and hash zones counts must all be zero or all non-zero
[23218.829947] device-mapper: ioctl: error adding target to table
--vdoHashZoneThreads produce different error, more in BZ 1511085.
Version-Release number of selected component (if applicable):
vdo-6.1.0.34-8
How reproducible:
100%
Steps to Reproduce:
1.vdo create --device /dev/sdc --name vdo --verbose --vdoPhysicalThreads 0
2.vdo create --device /dev/sdc --name vdo --verbose --vdoLogicalThreads 0
Actual results:
device-mapper catching error, giving info in console. Not enough info in terminal
Expected results:
vdo catching the error, requesting all 3 to be 0
Additional info:
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/RHEA-2018:0871
Description of problem: As subject says, creating VDO with only 1 of those options specified leads to VDO actually trying to create it and device-mapper catching the error. # vdo create --device /dev/sdc --name vdo --verbose --vdoLogicalThreads 0 Creating VDO vdo modprobe kvdo vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdc vdodumpconfig /dev/sdc Starting VDO vdo dmsetup status vdo modprobe kvdo dmsetup create vdo --table '0 11721045168 dedupe /dev/sdc 4096 disabled 0 32768 16380 on sync vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=0,physical=1' vdo: ERROR - Could not set up device mapper for vdo Removing VDO vdo Stopping VDO vdo dmsetup status vdo vdo: ERROR - device-mapper: reload ioctl on vdo failed: Invalid argument console: [B[22976.417374] device-mapper: table: 253:2: dedupe: Logical, physical, and hash zones counts must all be zero or all non-zero [22976.428426] device-mapper: ioctl: error adding target to table # vdo create --device /dev/sdc --name vdo --verbose --vdoPhysicalThreads 0 Creating VDO vdo modprobe kvdo vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/sdc vdodumpconfig /dev/sdc Starting VDO vdo dmsetup status vdo modprobe kvdo dmsetup create vdo --table '0 11721045168 dedupe /dev/sdc 4096 disabled 0 32768 16380 on sync vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=0' vdo: ERROR - Could not set up device mapper for vdo Removing VDO vdo Stopping VDO vdo dmsetup status vdo vdo: ERROR - device-mapper: reload ioctl on vdo failed: Invalid argument [root@storageqe-24 raid]# console: [23218.818914] device-mapper: table: 253:2: dedupe: Logical, physical, and hash zones counts must all be zero or all non-zero [23218.829947] device-mapper: ioctl: error adding target to table --vdoHashZoneThreads produce different error, more in BZ 1511085. Version-Release number of selected component (if applicable): vdo-6.1.0.34-8 How reproducible: 100% Steps to Reproduce: 1.vdo create --device /dev/sdc --name vdo --verbose --vdoPhysicalThreads 0 2.vdo create --device /dev/sdc --name vdo --verbose --vdoLogicalThreads 0 Actual results: device-mapper catching error, giving info in console. Not enough info in terminal Expected results: vdo catching the error, requesting all 3 to be 0 Additional info: