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:
Using directly DM it is possible to create 2 VDO devices using the same storage with little to no issues. The 2nd VDO fails to load the index, but the device is usable by both at the same time.
# vdoformat /dev/sda
Logical blocks defaulted to 2435905347 blocks.
# dmsetup create vdo0 --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo0"
# dmsetup create vdo1 --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo1"
# dmsetup table
vdo1: 0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo1
vdo0: 0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo0
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 9.1T 0 disk
├─vdo0 253:0 0 500K 0 dm
└─vdo1 253:1 0 500K 0 dm
syslog:
[ 6740.323954] kvdo2:dmsetup: WARNING: Running in sync mode atop a device supporting flushes is dangerous!
[ 6751.612181] kvdo3:dmsetup: WARNING: Running in sync mode atop a device supporting flushes is dangerous!
[ 6751.688810] kvdo3:reqQ: Device was dirty, rebuilding reference counts
[ 6753.464640] uds: kvdo3:dedupeQ: index could not be loaded: UDS Error: Index not saved cleanly (1069)
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. vdoformat /dev/sda
2. dmsetup create vdo0 --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo0"
3. dmsetup create vdo1 --table "0 1000 vdo V2 /dev/sda 2441609216 4096 32768 16380 off sync vdo1"
Actual results:
both VDO created and running
Expected results:
2nd VDO fails to create as the device is already in use by other VDO.
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/RHBA-2020:1782