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:
VDO is a device mapper target with deduplication and compression features.
Until recently VDO did not have a magic number or UUID.  blkid support for VDO
is needed, so utilities using blkid can be informed that the a given storage device is being used by VDO.


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


How reproducible:
100% can't identify VDO volumes
Create a VDO volume


Steps to Reproduce:
1. vdo create --name=vdo1 --device=/dev/sdb --vdoLogicalSize=10T
2. # blkid /dev/sdb


Actual results:
# blkid /dev/sdb
# <nothing>

Expected results:
# blkid /dev/sdb
# /dev/sdb: UUID="<string>" TYPE="VDO"

Additional info:

The magic number is the first 8 bytes, with value 'dmvdo001' of the volume; the UUID is the 16 bytes starting 40 bytes into the volume. I could probably draw up quickly a superblocks/vdo.c if desired.

(In reply to Sweet Tea Dorminy from comment #3)
> I could probably draw up quickly a superblocks/vdo.c if desired.

Thanks! It would be nice. The ideal solution is to prepare a patch for upstream tree:

   https://github.com/karelzak/util-linux

I'll backport it to RHEL7. See also libblkid/src/superblocks/lvm.c where are another DM targets, maybe we can add DM_VDO there.

It would be also nice to have a test image with the superblock (just dd(1) first sectors from the device).

https://github.com/karelzak/util-linux/pull/547

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-2018:0936